[Desktop-packages] [Bug 1964401] Re: Software Sources/software-properties-qt privilege escalation not accepting password
** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** No longer affects: software-properties (Ubuntu) ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1964401 Title: Software Sources/software-properties-qt privilege escalation not accepting password Status in plasma-discover package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: New Bug description: 1) lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 2) package version - apt-cache policy pkgname' plasma-discover: Installed: 5.24.2.1-0ubuntu1 software-properties-qt: Installed: 0.99.19 3) expected to happen * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * enter user password * software-properties-qt opens 4) happened instead * In Discover: Settings > Software Sources * opens a privilege escalation dialogue * insert known-correct user password * **does not accept known-correct user password** # Additional Info Note: described behaviour is for a post 20.04->22.04 devel daily upgrade found during a QA Testcase. Behaviour exists, but has slightly different symptoms in a virgin live 22.04 daily session (see below) * launching from terminal works as expected sudo software-properties-qt ## process & errors - post 20.04->22.04 devel daily upgrade * running Discover from terminal $ plasma-discover * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. * insert known-correct user password gives error on terminal: > kf.su: [ ./src/stubprocess.cpp : 225 ] Unknown request: "stop" > end * close password window gives error on terminal > Usage: /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu [options] command > Runs a program with elevated privileges. > Options: > -h, --help Displays help on commandline options. > [...] ## process & errors - live Kubuntu 22.04 daily similar behaviour, hoever password-asking window never appears. Terminal errors differ from above: * Settings > Software Sources gives error on terminal: > org.kde.kdesu: Daemon not safe (not sgid), not using it. > > Don't need password!! > >kf.su: [./src/stubprocess.cpp : 255 ] Unknown request: "ok" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-07 (2 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Package: plasma-discover 5.24.2.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Tags: jammy third-party-packages Uname: Linux 5.15.0-18-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-03-07 (2 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1964401/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
** Also affects: plasma-browser-integration (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: In Progress Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: In Progress Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Status in plasma-browser-integration package in Ubuntu: New Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. [Workaround] If you're using Ubuntu 22.04 LTS, you can install GNOME Shell extensions with this app. sudo apt install gnome-shell-extension-manager To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1959027]
Vlad, thanks for the hint! The xdg-desktop-portal-gtk package was not installed on my Jammy test system. After installing it, all three remaing UI issues (wrong theme, wrong cursor, wrong font size) seem to be fixed! So it would help, at least on Kubuntu, if the xdg-desktop-portal-gtk package was installed by default. -- 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/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1959027/+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 1959027]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #4) > Does that happen with other GTK apps ran via snap? I don't think we have > control about the GTK theme in use. Interesting, I tested two other GTK3 apps via snap (Inkscape and eog): * when running under Plasma Wayland, they also used the "wrong" GTK theme (Adwaita instead of Breeze), just like Firefox. And they had the same ugly font rendering like in the GTK file dialog on my screenshot. * on Plasma X11, all three apps (Inkscape, eog and Firefox) correctly used Breeze as GTK theme! So it seems to me there is a general issue in Snap when running GTK3 apps under Plasma Wayland, which also affects Firefox. -- 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/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1959027/+subscriptions -- Mailing list: htt
[Desktop-packages] [Bug 1959027]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #2) > Does this work on the nightly? I would expect bug 1734934 to have fixed this. Two of the issues seem to be fixed in nightly: 1. Dark theme is now correctly enabled without requiring a session restart first. 5. Firefox correctly uses KDE file dialogs now (with correctly rendered fonts!) The following three issues remain unchanged: 2. Font size of the UI elements is too big. 3. Wrong GTK theme is used (Adwaita, instead of Breeze Dark). 4. Mouse cursor uses wrong theme and is too big (it changes, when moving in and out of the Firefox window). I installed nightly by running 'snap refresh --edge firefox'. -- 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/1959027 Title: [snap] Various UI and theming issues when running in Plasma Wayland session Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1959027/+subscriptions -- Mailing list: https://
[Desktop-packages] [Bug 1959027] Re: Various UI and theming issues in Firefox snap when running in Plasma Wayland session
** Attachment added: "Second screenshot: GTK File dialog with distorted fonts" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+attachment/5557396/+files/Screenshot_20220125_165558.png -- 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/1959027 Title: Various UI and theming issues in Firefox snap when running in Plasma Wayland session Status in firefox package in Ubuntu: New Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1959027/+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 1959027] [NEW] Various UI and theming issues in Firefox snap when running in Plasma Wayland session
Public bug reported: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE apps on screenshots). 3. It apparently doesn't use Breeze (light or dark) as the UI theme, but something else (Adwaita I guess). 4. The mouse cursor uses the wrong theme and is too big (it changes visible if move the cursor in and out of the Firefox window). 5. If I click e.g. on "File -> Open file...", the file dialog is not the one from KDE but the one from GTK/Gnome. And the UI text is displayed in a rather jagged/distorted way (see screenshot). The issues described above do _not_ appear: * If I run Firefox as snap in Plasma X11 session. * If I run Firefox as deb (both Plasma Wayland and X11 session work fine). Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 96.0.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 BuildID: 20220119190439 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: KDE Date: Tue Jan 25 17:19:38 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-25 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220125.1) IpRoute: default via 192.168.178.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.44 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=96.0.2/20220119190439 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Wrong theme, UI font too big" https://bugs.launchpad.net/bugs/1959027/+attachment/5557383/+files/Screenshot_20220125_165617.png -- 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/1959027 Title: Various UI and theming issues in Firefox snap when running in Plasma Wayland session Status in firefox package in Ubuntu: New Bug description: Hello, after installing the current live image of Kubuntu Jammy, I tested the preinstalled Firefox snap on the Plasma Wayland session (which I use by default), and discovered multiple UI and theming issues: 1. I had switched my global theme to Breeze Dark. Nevertheless Firefox used a light theme when I launched it for the first time. Interestingly, at further runs Firefox properly came up with a dark theme. But I had restarted my session in between and also had removed and reinstalled the Firefox snap, so it's possible that one of these actions triggered Firefox to finally use a dark theme. 2. The font size in the UI is too big (compare with other KDE ap
[Desktop-packages] [Bug 1941752]
(In reply to Jan Rathmann from comment #15) > For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2 from > kubuntu-backports-ppa. Please disregard this comment - I totally forgot that I had installed a patched version of exiv2 (with the change described in Comment 4) to workaround the bug, sorry for causing confusion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752]
For me this seems to be fixed under Kubuntu 21.10 with Gwenview 21.08.2 from kubuntu-backports-ppa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
The following change in CVE-2021-37620-3.patch is responsible:
--- exiv2-0.27.3.orig/src/tags_int.cpp
+++ exiv2-0.27.3/src/tags_int.cpp
@@ -2865,7 +2865,7 @@ namespace Exiv2 {
}
std::string stringValue = value.toString();
-if (stringValue[19] == 'Z') {
+if (stringValue.at(19) == 'Z') {
stringValue = stringValue.substr(0, 19);
}
for (size_t i = 0; i < stringValue.length(); ++i) {
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to exiv2 in Ubuntu.
https://bugs.launchpad.net/bugs/1941752
Title:
Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
images exported by darktable
Status in Gwenview:
Unknown
Status in exiv2 package in Ubuntu:
New
Status in gwenview package in Ubuntu:
New
Bug description:
Since the recent security update of exiv2, Gwenview crashes when
trying to open image files that got exported by darktable.
Steps to reproduce:
* Make a test installation of Kubuntu 21.04 in VirtualBox
* Install all updates
* Install darktable
* Copy one of the images in /usr/share/wallpapers (or any other image) to
your home directory and open it with darktable
* Within darktable, export a copy of the image (no need to do any actual
modifications)
* Try to open that copy with Gwenview. Gwenview will crash.
I'm attaching a crash report hinting that this is related to exiv2.
Temporary workaround:
If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.
I don't know if the underlying cause is actually some bug in exiv2,
Gwenview or darktable.
Kind regards, Jan
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: libexiv2-27 0.27.3-3ubuntu1.5
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Thu Aug 26 15:16:47 2021
InstallationDate: Installed on 2021-08-26 (0 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
SourcePackage: exiv2
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Relevant terminal output from crash: terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 108229 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
CVE-2021-37620-3.patch is responsible. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-37620 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
** Also affects: gwenview (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752] [NEW] Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Public bug reported: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gwenview Importance: Unknown Status: Unknown ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Crash report of Gwenview" https://bugs.launchpad.net/bugs/1941752/+attachment/5520895/+files/gwenview-20210826-153914.kcrash ** Bug watch added: KDE Bug Tracking System #441121 https://bugs.kde.org/show_bug.cgi?id=441121 ** Also affects: gwenview via https://bugs.kde.org/show_bug.cgi?id=441121 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: New Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 341024] Re: Use liberation fonts in firefox by default for better website layout
Yes, this bug is fixed of course since years! Totally forgot about this ancient report... ** Changed in: firefox (Ubuntu) Status: Incomplete => Fix Released -- 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/341024 Title: Use liberation fonts in firefox by default for better website layout Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: firefox Hello, with the fonts that are currently used by default in Firefox to render websites (I guess DejaVu), the layout on some sites is a bit distorted, you can see this in the screenshots below (taken on a fresh Jaunty installation). The cause for this seems to be that these fonts are a bit bigger than the default Microsoft fonts (Arial, Times New Roman, ...), on whose size some web layouter obviously rely. A possible workaround would be to use the Liberation Fonts for Firefox which are metric compatible with the Microsoft ones: http://en.wikipedia.org/wiki/Liberation_fonts I am doing this on my machine for some time now by selecting them manually in "Edit -> Preferences -> Content -> Fonts & Colors -> Extended...", they look very good. The Liberations Fonts package seems to be in Main now (ttf-liberation). Kind regards, Jan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/341024/+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 1898334] [NEW] When starting Chromium, desktop-launch sometimes moves personal files and folders on separate partition to my home directoy
Public bug reported: Hello, this bug was originally reported on https://github.com/ubuntu/snapcraft- desktop-helpers/issues/205 where I added a comment with my experience ( https://github.com/ubuntu/snapcraft-desktop- helpers/issues/205#issuecomment-696781060 ). I thought creating a bug report on Launchpad in addition would maybe help to track this issue. The following has happened to me for two times so far: 1) Tried to start Chromium (one time it was via UI/.desktop file, one time it was by running 'chromium-browser' in terminal) 2) Chromium didn't launch but instead the helper script 'desktop-launch' (in /snap/chromium/1320/bin/desktop-launch) moved files and folders that are located on a separate partition to my home directory (detailed description below) until I killed it. Luckily I had a backup, but it caused some work to restore everything. Really eerie experience, when all of a sudden my files began to get messed up. My setup is as follows: The / and /home directory of my main installation (Kubuntu 20.04) are on a SSD drive, while there is also a much bigger HDD as a second drive where I store all of my "bigger" data (photos, music, videos etc.). The HDD partition is mounted unter /mnt/my_hdd and there are symbolic links in my home directory to its directories (e.g. ~/photos is a symlink to /mnt/my_hdd/photos). Now what desktop-launch seemed to do was to move the files and directorys of this symlinked directories (HDD) to my home directory (SSD). E.g. ~/photos/* (actually stored on /mnt/my_hdd/photos/) was moved to ~/*. Subdirectories like photos/album1 were kept intact, but all the content of the "top level folders" of my HDD (music, videos, photos, ...) got mixed up together in my home directory. In both cases I noticed there's something going wrong and managed to kill desktop-launch after a short time, otherwise, it would have filled up all the small space on my SSD. This can be a cause of data loss without having a backup, because 1) it destroys directory structures by moving files/folders from different directories into one (as described above), and 2) related to that mv could silently overwrite files with different ones which have the same name. Can I provide any further information to help to debug this? I'm not sure how I can reproduce this, since in all cases except the two ones recently Chromium startup worked just fine. Fortunately I'm using Chromium only for testing purposes, so I don't launch it that often and can make btrfs snapshots before doing so and taking that risk again. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Oct 3 09:19:51 2020 InstallationDate: Installed on 2020-04-08 (177 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1898334 Title: When starting Chromium, desktop-launch sometimes moves personal files and folders on separate partition to my home directoy Status in chromium-browser package in Ubuntu: New Bug description: Hello, this bug was originally reported on https://github.com/ubuntu /snapcraft-desktop-helpers/issues/205 where I added a comment with my experience ( https://github.com/ubuntu/snapcraft-desktop- helpers/issues/205#issuecomment-696781060 ). I thought creating a bug report on Launchpad in addition would maybe help to track this issue. The following has happened to me for two times so far: 1) Tried to start Chromium (one time it was via UI/.desktop file, one time it was by running 'chromium-browser' in terminal) 2) Chromium didn't launch but instead the helper script 'desktop-launch' (in /snap/chromium/1320/bin/desktop-launch) moved files and folders that are located on a separate partition to my home directory (detailed description below) until I killed it. Luckily I had a backup, but it caused some work to restore everything. Really eerie experience, when all of a sudden my files began to get messed up. My setup is as follows: The / and /home directory of my main installation (Kubuntu 20.04) are on a SSD drive, while there is also a much bigger HDD as a second drive where I store all of my "bigger" data (photos, music, videos etc.). The HDD partition is mounted unter /mnt/my_hdd and there are symbolic links in my home directory to its directories (e.g. ~/photos is a symlink to /mnt/my_hdd/photos). Now what de
[Desktop-packages] [Bug 1675496] Re: Scrollbars are tiny in Firefox 52
The described issue with the scrollbar size still exists on Bionic (and
all newer Firefox versions).
** Changed in: firefox (Ubuntu)
Status: Invalid => Confirmed
** Summary changed:
- Scrollbars are tiny in Firefox 52
+ Scrollbars are tiny in Firefox (since FF 52)
** Description changed:
+ == Update 2018-02-27: While this report was created for Firefox 52 under
+ Ubuntu 16.10, it is still valid for all newer Firefox version/Ubuntu
+ releases. ==
+
In Firefox 52, the size of scrollbars has become smaller so that it is
really tiny and hard to grab by the mouse. For me, this is a usability
issue.
The scrollbars were considerably bigger in Firefox 51 and previous
releases. To illustrate this, I have attached two screeenshots for
comparision between Firefox 51 and 52.
While other GTK3-applications (e.g. Gedit) also have very slim
scrollbars, they on the other hand have a mechanismn that makes their
scrollbars broaden automatically when you move the mouse over them, so
grabbing them isn't an issue. If the same would be possible in Firefox,
this would of course be also an acceptable resolution.
Kind regards,
Jan
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: firefox 52.0.1+build2-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-43.46-generic 4.8.17
Uname: Linux 4.8.0-43-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: jan2427 F pulseaudio
- /dev/snd/controlC0: jan2427 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: jan2427 F pulseaudio
+ /dev/snd/controlC0: jan2427 F pulseaudio
BuildID: 20170317212642
Channel: Unavailable
CurrentDesktop: Unity
Date: Thu Mar 23 17:48:02 2017
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePlugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
- # interfaces(5) file used by ifup(8) and ifdown(8)
- auto lo
- iface lo inet loopback
+ # interfaces(5) file used by ifup(8) and ifdown(8)
+ auto lo
+ iface lo inet loopback
InstallationDate: Installed on 2016-10-11 (163 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
IpRoute:
- default via 192.168.2.1 dev enp4s0 proto static metric 100
- 192.168.2.0/24 dev enp4s0 proto kernel scope link src 192.168.2.110
metric 100
+ default via 192.168.2.1 dev enp4s0 proto static metric 100
+ 192.168.2.0/24 dev enp4s0 proto kernel scope link src 192.168.2.110
metric 100
IwConfig:
- enp4s0no wireless extensions.
-
- vboxnet0 no wireless extensions.
-
- lono wireless extensions.
+ enp4s0no wireless extensions.
+
+ vboxnet0 no wireless extensions.
+
+ lono wireless extensions.
MostRecentCrashID: bp-fd3ffe0d-b587-4fd6-9f51-0e92e2161201
Profile0IncompatibleExtensions:
- English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
- Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
- English (GB) Language Pack - langpack-en...@firefox.mozilla.org
- Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
+ English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
+ Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
+ English (GB) Language Pack - langpack-en...@firefox.mozilla.org
+ Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile0Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile0PrefSources:
- prefs.js
- user.js
-
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
+ prefs.js
+ user.js
+
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
Profile1IncompatibleExtensions:
- English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
- Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
- English (GB) Language Pack - langpack-en...@firefox.mozilla.org
- Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
+ English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
+ Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
+ English (GB) Language Pack - langpack-en...@firefox.mozilla.org
+ Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile1Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile1PrefSources:
- prefs.js
- user.js
+ prefs.js
+ user.js
Profile2IncompatibleExtensions:
-
[Desktop-packages] [Bug 1675496] Re: Scrollbars are tiny in Firefox 52
@madbiologist
Yes, this would be an acceptable solution, but on my system (Yakkety) the
scrollbars in Firefox always stay slim and never broaden, regardless if I move
the mouse over the slider or some other place on the scrollbar. Is this
different on your installation?
--
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/1675496
Title:
Scrollbars are tiny in Firefox 52
Status in firefox package in Ubuntu:
New
Bug description:
In Firefox 52, the size of scrollbars has become smaller so that it is
really tiny and hard to grab by the mouse. For me, this is a usability
issue.
The scrollbars were considerably bigger in Firefox 51 and previous
releases. To illustrate this, I have attached two screeenshots for
comparision between Firefox 51 and 52.
While other GTK3-applications (e.g. Gedit) also have very slim
scrollbars, they on the other hand have a mechanismn that makes their
scrollbars broaden automatically when you move the mouse over them, so
grabbing them isn't an issue. If the same would be possible in
Firefox, this would of course be also an acceptable resolution.
Kind regards,
Jan
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: firefox 52.0.1+build2-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-43.46-generic 4.8.17
Uname: Linux 4.8.0-43-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jan2427 F pulseaudio
/dev/snd/controlC0: jan2427 F pulseaudio
BuildID: 20170317212642
Channel: Unavailable
CurrentDesktop: Unity
Date: Thu Mar 23 17:48:02 2017
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePlugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-10-11 (163 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
IpRoute:
default via 192.168.2.1 dev enp4s0 proto static metric 100
192.168.2.0/24 dev enp4s0 proto kernel scope link src 192.168.2.110
metric 100
IwConfig:
enp4s0no wireless extensions.
vboxnet0 no wireless extensions.
lono wireless extensions.
MostRecentCrashID: bp-fd3ffe0d-b587-4fd6-9f51-0e92e2161201
Profile0IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile0Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile0PrefSources:
prefs.js
user.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
Profile1IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile1Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile1PrefSources:
prefs.js
user.js
Profile2IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile2Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile2PrefSources: prefs.js
Profile3IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile3Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile3PrefSources: prefs.js
Profile4Extensions: extensions.sqlite corrupt or missing
Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile4Locales: extensions.sqlite corrupt or missing
Profile4Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashpla
[Desktop-packages] [Bug 1675334] Re: nvidia 375.39 package makes weird screen appearance on resume
*** This bug is a duplicate of bug 1667158 *** https://bugs.launchpad.net/bugs/1667158 ** This bug has been marked a duplicate of bug 1667158 Borders of pop-up windows are displayed badly -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1675334 Title: nvidia 375.39 package makes weird screen appearance on resume Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Bug description: I recently received new proprietary nvidia driver package (nvidia 375.39) and my computer screen makes very weird apparance, rainbow-like frame around windows upon resume. It is very difficult to explain that situation, additional lines on all window borders and makes window buttons in upper window frame very invisible, attached in this bug report. I am using NVIDIA GeForce 560 Ti graphics card and I had not met such experience before. My system is Ubuntu 16.04 (Xenial) with all latest patches applied. Here's summary of my graphics environment: lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) sudo lshw -C video *-display description: VGA compatible controller product: GF114 [GeForce GTX 560 Ti] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:01:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:32 memory:f800-f9ff memory:d000-d7ff memory:dc00-dfff ioport:af00(size=128) memory:fa00-fa07 I temporarily reverted my driver to older 340.102 proprietary and it is no problem for sleep / resume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1675334/+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 1675496] Re: Scrollbars are small in Firefox 52
** Attachment added: "Bigger scrollbars in Firefox 51"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1675496/+attachment/4843527/+files/FF-Scrollbars%2051.png
** Summary changed:
- Scrollbars are small in Firefox 52
+ Scrollbars are tiny in Firefox 52
--
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/1675496
Title:
Scrollbars are tiny in Firefox 52
Status in firefox package in Ubuntu:
New
Bug description:
In Firefox 52, the size of scrollbars has become smaller so that it is
really tiny and hard to grab by the mouse. For me, this is a usability
issue.
The scrollbars were considerably bigger in Firefox 51 and previous
releases. To illustrate this, I have attached two screeenshots for
comparision between Firefox 51 and 52.
While other GTK3-applications (e.g. Gedit) also have very slim
scrollbars, they on the other hand have a mechanismn that makes their
scrollbars broaden automatically when you move the mouse over them, so
grabbing them isn't an issue. If the same would be possible in
Firefox, this would of course be also an acceptable resolution.
Kind regards,
Jan
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: firefox 52.0.1+build2-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-43.46-generic 4.8.17
Uname: Linux 4.8.0-43-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jan2427 F pulseaudio
/dev/snd/controlC0: jan2427 F pulseaudio
BuildID: 20170317212642
Channel: Unavailable
CurrentDesktop: Unity
Date: Thu Mar 23 17:48:02 2017
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePlugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-10-11 (163 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
IpRoute:
default via 192.168.2.1 dev enp4s0 proto static metric 100
192.168.2.0/24 dev enp4s0 proto kernel scope link src 192.168.2.110
metric 100
IwConfig:
enp4s0no wireless extensions.
vboxnet0 no wireless extensions.
lono wireless extensions.
MostRecentCrashID: bp-fd3ffe0d-b587-4fd6-9f51-0e92e2161201
Profile0IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile0Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile0PrefSources:
prefs.js
user.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
Profile1IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile1Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile1PrefSources:
prefs.js
user.js
Profile2IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile2Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile2PrefSources: prefs.js
Profile3IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile3Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile3PrefSources: prefs.js
Profile4Extensions: extensions.sqlite corrupt or missing
Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile4Locales: extensions.sqlite corrupt or missing
Profile4Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
[Desktop-packages] [Bug 1675496] [NEW] Scrollbars are tiny in Firefox 52
Public bug reported:
In Firefox 52, the size of scrollbars has become smaller so that it is
really tiny and hard to grab by the mouse. For me, this is a usability
issue.
The scrollbars were considerably bigger in Firefox 51 and previous
releases. To illustrate this, I have attached two screeenshots for
comparision between Firefox 51 and 52.
While other GTK3-applications (e.g. Gedit) also have very slim
scrollbars, they on the other hand have a mechanismn that makes their
scrollbars broaden automatically when you move the mouse over them, so
grabbing them isn't an issue. If the same would be possible in Firefox,
this would of course be also an acceptable resolution.
Kind regards,
Jan
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: firefox 52.0.1+build2-0ubuntu0.16.10.1
ProcVersionSignature: Ubuntu 4.8.0-43.46-generic 4.8.17
Uname: Linux 4.8.0-43-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jan2427 F pulseaudio
/dev/snd/controlC0: jan2427 F pulseaudio
BuildID: 20170317212642
Channel: Unavailable
CurrentDesktop: Unity
Date: Thu Mar 23 17:48:02 2017
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePlugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-10-11 (163 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008)
IpRoute:
default via 192.168.2.1 dev enp4s0 proto static metric 100
192.168.2.0/24 dev enp4s0 proto kernel scope link src 192.168.2.110 metric
100
IwConfig:
enp4s0no wireless extensions.
vboxnet0 no wireless extensions.
lono wireless extensions.
MostRecentCrashID: bp-fd3ffe0d-b587-4fd6-9f51-0e92e2161201
Profile0IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile0Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile0PrefSources:
prefs.js
user.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
Profile1IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile1Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile1PrefSources:
prefs.js
user.js
Profile2IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile2Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile2PrefSources: prefs.js
Profile3IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Deutsch (DE) Language Pack - langpack...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
Profile3Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile3PrefSources: prefs.js
Profile4Extensions: extensions.sqlite corrupt or missing
Profile4IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile4Locales: extensions.sqlite corrupt or missing
Profile4Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile4PrefSources: prefs.js
Profile4Themes: extensions.sqlite corrupt or missing
Profile6Extensions: extensions.sqlite corrupt or missing
Profile6IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Profile6Locales: extensions.sqlite corrupt or missing
Profile6Plugins: Shockwave Flash -
/usr/lib/flashplugin-installer/libflashplayer.so
Profile6PrefSources: prefs.js
Profile6Themes: extensions.sqlite corrupt or missing
RfKill:
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F14
[Desktop-packages] [Bug 1621751] Re: package nvidia-opencl-icd-367 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl-icd-367
*** This bug is a duplicate of bug 1619829 *** https://bugs.launchpad.net/bugs/1619829 ** This bug has been marked a duplicate of bug 1619829 package nvidia-opencl-icd-367 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl-icd-367 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/1621751 Title: package nvidia-opencl-icd-367 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl- icd-367 Status in nvidia-graphics-drivers-367 package in Ubuntu: New Bug description: upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-opencl-icd-367 (not installed) ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Sep 9 08:25:49 2016 ErrorMessage: conflicting packages - not installing nvidia-opencl-icd-367 InstallationDate: Installed on 2016-04-21 (140 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: nvidia-graphics-drivers-367 Title: package nvidia-opencl-icd-367 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl-icd-367 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1621751/+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 1325940] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518428/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dm
[Desktop-packages] [Bug 1325940] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518426/+files/UdevLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chas
[Desktop-packages] [Bug 1325940] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518424/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0
[Desktop-packages] [Bug 1325940] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518419/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.a
[Desktop-packages] [Bug 1325940] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518422/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0
[Desktop-packages] [Bug 1325940] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518415/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0
[Desktop-packages] [Bug 1325940] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518425/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis
[Desktop-packages] [Bug 1325940] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518423/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version:
[Desktop-packages] [Bug 1325940] xserver.outputs.txt
apport information ** Attachment added: "xserver.outputs.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518431/+files/xserver.outputs.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version
[Desktop-packages] [Bug 1325940] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518429/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis
[Desktop-packages] [Bug 1325940] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518416/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chas
[Desktop-packages] [Bug 1325940] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518418/+files/LightdmLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dm
[Desktop-packages] [Bug 1325940] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518420/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.a
[Desktop-packages] [Bug 1325940] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518427/+files/XorgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chas
[Desktop-packages] [Bug 1325940] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518430/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.ch
[Desktop-packages] [Bug 1325940] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518421/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0
[Desktop-packages] [Bug 1325940] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518417/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.ver
[Desktop-packages] [Bug 1325940] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518414/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0
[Desktop-packages] [Bug 1325940] Re: Desktop sometimes comes up with undisplayable screen resolution
apport information ** Tags added: apport-collected ubuntu ** Description changed: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver- xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.14.1-0ubuntu3.18 + Architecture: amd64 + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: None + CurrentDesktop: XFCE + DistUpgraded: Fresh install + DistroCodename: trusty + DistroRelease: Ubuntu 14.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes + GraphicsCard: + Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) +Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] +Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] + InstallationDate: Installed on 2014-04-22 (570 days ago) + InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) + LightdmGreeterLog: + ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden + g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. + LightdmGreeterLogOld: + ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden + g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. + MachineType: MSI MS-6741 + Package: xorg 1:7.7+1ubuntu8.1 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 + Tags: trusty ubuntu + Uname: Linux 3.13.0-63-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo + _MarkForUpload: True + dmi.bios.date: 04/02/01 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: Version 07.00T + dmi.board.name: MS-6741 + dmi.board.vendor: MSI + dmi.board.version: 1.0 + dmi.chassis.asset.tag: 0123ABC + dmi.chassis.type: 3 + dmi.chassis.vendor: Uknown Chassis Manufacture + dmi.chassis.version: Version 1.00 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrVersion07.00T:bd04/02/01:svnMSI:pnMS-6741:pvr1.0:rvnMSI:rnMS-6741:rvr1.0:cvnUknownChassisManufacture:ct3:cvrVersion1.00: + dmi.product.name: MS-6741 + dmi.
[Desktop-packages] [Bug 1325940] BootLog.txt
apport information ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1325940/+attachment/4518413/+files/BootLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932a] Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:932b] InstallationDate: Installed on 2014-04-22 (570 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: ** (lightdm-gtk-greeter:9382): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:6675): WARNING **: Failed to load user image: Datei »/home/grete/.face« konnte nicht geöffnet werden: Datei oder Verzeichnis nicht gefunden g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: MSI MS-6741 Package: xorg 1:7.7+1ubuntu8.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic root=UUID=b7a652e9-aea3-4c8a-bf11-32ec8d22b3bb ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25 Tags: trusty ubuntu Uname: Linux 3.13.0-63-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo _MarkForUpload: True dmi.bios.date: 04/02/01 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Version 07.00T dmi.board.name: MS-6741 dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chas
[Desktop-packages] [Bug 1503602] [NEW] Eog should show an Open with... menu item in the global menu under Unity
Public bug reported: Hello, currently Eog in Wily lacks a discoverable "Open with..." menu item under "Image" in its menu bar when using Unity, so I propose to add it there. The "Open with..." functionality is currently only avaiable from the context menu when you right click somewhere in the image, but that's not very discoverable. When using Eog under Ubuntu Gnome, the "Open with.." item is integrated into the menu of the "Hamburger button" in the toolbar on the top right. Previous versions of Eog (untill Vivid) had the ability to customize the toolbar and add an "Edit image..." button, which I'm missing a bit, and the "Open with..." functionality is the most viable replacement for this at the moment, so it should not be made too hard for existing users to discover that. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: eog 3.16.3-1ubuntu2 Uname: Linux 4.3.0-040300rc4-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 7 10:48:12 2015 InstallationDate: Installed on 2015-10-03 (3 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1503602 Title: Eog should show an Open with... menu item in the global menu under Unity Status in eog package in Ubuntu: New Bug description: Hello, currently Eog in Wily lacks a discoverable "Open with..." menu item under "Image" in its menu bar when using Unity, so I propose to add it there. The "Open with..." functionality is currently only avaiable from the context menu when you right click somewhere in the image, but that's not very discoverable. When using Eog under Ubuntu Gnome, the "Open with.." item is integrated into the menu of the "Hamburger button" in the toolbar on the top right. Previous versions of Eog (untill Vivid) had the ability to customize the toolbar and add an "Edit image..." button, which I'm missing a bit, and the "Open with..." functionality is the most viable replacement for this at the moment, so it should not be made too hard for existing users to discover that. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: eog 3.16.3-1ubuntu2 Uname: Linux 4.3.0-040300rc4-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 7 10:48:12 2015 InstallationDate: Installed on 2015-10-03 (3 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1503602/+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 1434986] Re: Not working network connection after boot
Like carlix, I didn't see this bug so far under Wily. -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1499389] [NEW] HP Photosmart D5460 prints text in gray instead of black when A4 borderless is chosen
Public bug reported: Hello, if I print black text on my HP Photosmart D5460, the output is grey instead of black when choose "A4 borderless" as media size. Steps to reproduce: 1. Start LibreOffice Writer, write some text 2. Click "File -> Print" 3. In the print dialogue, check "Use only paper size from printer settings" (under the "Options"-tab) 4. On the "General"-tab, select the printer and click on properties 5. In the properties dialogue, select "A4 borderless" as paper size (optionally set print quality to "draft" and output mode to "black only grayscale", my preferred settings) 6. Start the print. Now the printed text is grey instead of black, I have attached a photo of how the output looks compared to normal output (when media size is set to "A4" non-borderless). I have also attached the file (printout) with the data that would go to the printer when printing on "A4 borderless" according to the guide on https://wiki.ubuntu.com/DebuggingPrintingProblems#Getting_the_data_which_would_go_to_the_printer Kind regards; Jan ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Thu Sep 24 15:57:48 2015 InstallationDate: Installed on 2015-09-17 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150916) Lpstat: device for Photosmart-D5400-series: hp:/usb/Photosmart_D5400_series?serial=MY95A990G204V3 device for test: /tmp/printout MachineType: Gigabyte Technology Co., Ltd. P35-DS3 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Photosmart-D5400-series.ppd', '/etc/cups/ppd/test.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Photosmart-D5400-series.ppd: Permission denied grep: /etc/cups/ppd/test.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/@/vmlinuz root=/dev/mapper/internal--hdd-test1 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "printout" https://bugs.launchpad.net/bugs/1499389/+attachment/4473324/+files/printout -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1499389 Title: HP Photosmart D5460 prints text in gray instead of black when A4 borderless is chosen Status in cups package in Ubuntu: New Bug description: Hello, if I print black text on my HP Photosmart D5460, the output is grey instead of black when choose "A4 borderless" as media size. Steps to reproduce: 1. Start LibreOffice Writer, write some text 2. Click "File -> Print" 3. In the print dialogue, check "Use only paper size from printer settings" (under the "Options"-tab) 4. On the "General"-tab, select the printer and click on properties 5. In the properties dialogue, select "A4 borderless" as paper size (optionally set print quality to "draft" and output mode to "black only grayscale", my preferred settings) 6. Start the print. Now the printed text is grey instead of black, I have attached a photo of how the output looks compared to normal output (when media size is set to "A4" non-borderless). I have also attached the file (printout) with the data that would go to the printer when printing on "A4 borderless" according to the guide on https://wiki.ubuntu.com/DebuggingPrintingProblems#Getting_the_data_which_would_go_to_the_printer Kind regards; Jan ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Thu Sep 24 15:57:48 2015 InstallationDate: Installed on 2015-09-17 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150916) Lpstat: device for Photosmart-D5400-series: hp:/usb/Photosmart_D5400_series?serial=MY95A990G204V3 device for test: /tmp/printout M
[Desktop-packages] [Bug 1499389] Re: HP Photosmart D5460 prints text in gray instead of black when A4 borderless is chosen
In the photo, the last two lines are there to illustrate how a print with proper black looks like in comparison. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1499389 Title: HP Photosmart D5460 prints text in gray instead of black when A4 borderless is chosen Status in cups package in Ubuntu: New Bug description: Hello, if I print black text on my HP Photosmart D5460, the output is grey instead of black when choose "A4 borderless" as media size. Steps to reproduce: 1. Start LibreOffice Writer, write some text 2. Click "File -> Print" 3. In the print dialogue, check "Use only paper size from printer settings" (under the "Options"-tab) 4. On the "General"-tab, select the printer and click on properties 5. In the properties dialogue, select "A4 borderless" as paper size (optionally set print quality to "draft" and output mode to "black only grayscale", my preferred settings) 6. Start the print. Now the printed text is grey instead of black, I have attached a photo of how the output looks compared to normal output (when media size is set to "A4" non-borderless). I have also attached the file (printout) with the data that would go to the printer when printing on "A4 borderless" according to the guide on https://wiki.ubuntu.com/DebuggingPrintingProblems#Getting_the_data_which_would_go_to_the_printer Kind regards; Jan ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Thu Sep 24 15:57:48 2015 InstallationDate: Installed on 2015-09-17 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150916) Lpstat: device for Photosmart-D5400-series: hp:/usb/Photosmart_D5400_series?serial=MY95A990G204V3 device for test: /tmp/printout MachineType: Gigabyte Technology Co., Ltd. P35-DS3 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Photosmart-D5400-series.ppd', '/etc/cups/ppd/test.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Photosmart-D5400-series.ppd: Permission denied grep: /etc/cups/ppd/test.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/@/vmlinuz root=/dev/mapper/internal--hdd-test1 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1499389/+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 1499389] Re: HP Photosmart D5460 prints text in gray instead of black when A4 borderless is chosen
** Attachment added: "Photo of how the output of black text looks like with different settings" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1499389/+attachment/4473338/+files/P1050334.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1499389 Title: HP Photosmart D5460 prints text in gray instead of black when A4 borderless is chosen Status in cups package in Ubuntu: New Bug description: Hello, if I print black text on my HP Photosmart D5460, the output is grey instead of black when choose "A4 borderless" as media size. Steps to reproduce: 1. Start LibreOffice Writer, write some text 2. Click "File -> Print" 3. In the print dialogue, check "Use only paper size from printer settings" (under the "Options"-tab) 4. On the "General"-tab, select the printer and click on properties 5. In the properties dialogue, select "A4 borderless" as paper size (optionally set print quality to "draft" and output mode to "black only grayscale", my preferred settings) 6. Start the print. Now the printed text is grey instead of black, I have attached a photo of how the output looks compared to normal output (when media size is set to "A4" non-borderless). I have also attached the file (printout) with the data that would go to the printer when printing on "A4 borderless" according to the guide on https://wiki.ubuntu.com/DebuggingPrintingProblems#Getting_the_data_which_would_go_to_the_printer Kind regards; Jan ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: cups 2.1.0-4 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Thu Sep 24 15:57:48 2015 InstallationDate: Installed on 2015-09-17 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150916) Lpstat: device for Photosmart-D5400-series: hp:/usb/Photosmart_D5400_series?serial=MY95A990G204V3 device for test: /tmp/printout MachineType: Gigabyte Technology Co., Ltd. P35-DS3 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Photosmart-D5400-series.ppd', '/etc/cups/ppd/test.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Photosmart-D5400-series.ppd: Permission denied grep: /etc/cups/ppd/test.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/@/vmlinuz root=/dev/mapper/internal--hdd-test1 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1499389/+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 1434986] Re: Not working network connection after boot
Benjamin, I don't think the problem is related to a somehow messed up configuration (user or system wide), because as mentioned in #8, I can reproduce the bug by booting from a pristine live iso image. Or we a suffering from different bugs. -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1434986] Re: Not working network connection after boot
Benjamin, calix: Did you test booting your system with init=/sbin/upstart ? On my system this bug also appears when using Upstart as init, so this doesn't seem to be related to Systemd. -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1434986] Re: Not working network connection after boot
Some addtional information: - The bug also appears when booting a live session - If I setup my network via /etc/network/interfaces (= not managed by NetworkManager), the connection was always in a sane state, so it seems that NetworkManager is somehow responsible indeed. Kind regards, Jan -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1434986] Re: Not working network connection after boot
I suffer from the same problem and have just (accidently) reported a duplicate: #1445999 -- 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/1434986 Title: Not working network connection after boot Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1445999] [NEW] NetworkManager doesn't configure wired network connection properly
*** This bug is a duplicate of bug 1434986 *** https://bugs.launchpad.net/bugs/1434986 Public bug reported: Hello, after installing Vivid, nearly each time when I boot my PC NetworkManager fails to setup the (wired) connection to my router (via DHCP) properly. That means: - I can ping only the IP of my router. - If I try to ping e.g. ubuntu.com, this results either in "Unknown host" or "Network is down" error. - If I disconnect and connect again via the network-manager-applet, the connection is usually fine, so this is a workaround for me to get internet access. This didn't happen in any previous Ubuntu version. My home network setup is very plain, only a router that establishes the internet connection and assigns IP adresses via DHCP to all connected clients. The PC with Vivid running is connected via a wired link. The informations of the report were collected when the network connection was in faulty state (as mentioned above) in hope that it may give any hint to what's going wrong. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 19 21:48:18 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-04-16 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150415) IpRoute: 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.103 IwConfig: eth0 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Kabelnetzwerkverbindung 1 1654fa28-838d-4b95-821f-c6e0e8a6451d 802-3-ethernet 1429472871 So 19 Apr 2015 21:47:51 CEST yes no /org/freedesktop/NetworkManager/Settings/0 yes eth0activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Kabelnetzwerkverbindung 1 1654fa28-838d-4b95-821f-c6e0e8a6451d /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** This bug has been marked a duplicate of bug 1434986 Not working network connection after boot -- 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/1445999 Title: NetworkManager doesn't configure wired network connection properly Status in network-manager package in Ubuntu: New Bug description: Hello, after installing Vivid, nearly each time when I boot my PC NetworkManager fails to setup the (wired) connection to my router (via DHCP) properly. That means: - I can ping only the IP of my router. - If I try to ping e.g. ubuntu.com, this results either in "Unknown host" or "Network is down" error. - If I disconnect and connect again via the network-manager-applet, the connection is usually fine, so this is a workaround for me to get internet access. This didn't happen in any previous Ubuntu version. My home network setup is very plain, only a router that establishes the internet connection and assigns IP adresses via DHCP to all connected clients. The PC with Vivid running is connected via a wired link. The informations of the report were collected when the network connection was in faulty state (as mentioned above) in hope that it may give any hint to what's going wrong. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 19 2
[Desktop-packages] [Bug 1156318] Re: Missing pictures in help
*** This bug is a duplicate of bug 1136933 *** https://bugs.launchpad.net/bugs/1136933 ** This bug has been marked a duplicate of bug 1136933 Documentation images (e.g. of icons) missing -- 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/1156318 Title: Missing pictures in help Status in libreoffice package in Ubuntu: Confirmed Bug description: Open Libreoffice Writer and press F1 (or click on Libreoffice Help). Then a new window will open and the help will be shown, but no pictures are displayed in the help (see attached screenshot). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Sun Mar 17 20:45:00 2013 MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-02-25 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1156318/+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 1316658] Re: [Upstream] Misleading error dialog while printing in libreoffice writer
LibreOffice 1:4.2.4~rc2-0ubuntu1~trusty3 from https://launchpad.net/~libreoffice/+archive/libreoffice-4-2?field.series_filter=trusty seems to fix the bug for me. -- 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/1316658 Title: [Upstream] Misleading error dialog while printing in libreoffice writer Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Hi, libreoffice version 4.2.3.3 (current version from ubuntu 14.04 repository) shows an error dialog while printing a document: "Could not start printer. Please check your printer configuration" But printing starts and finishes without a visible problem. Excepted behavior: This dialog should not be displayed! This problems occurs on three installations, all running Kubuntu 14.04, and it's confirmed by various other users in my bugreport on bugs.freedesktop.org for other ubuntu variants, see https://bugs.freedesktop.org/show_bug.cgi?id=77894 for details The issue is reported to be fixed in libreoffice 4.2.4.1. Is it possible to backport the fix or to deploy a newer version in ubuntu repository? Regards, Thomas Version/Package information: -- Description:Ubuntu 14.04 LTS Release: 14.04 Package: libreoffice-writer Version: 1:4.2.3~rc3-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1316658/+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 1325940] Re: Desktop sometimes comes up with undisplayable screen resolution
This is the output of lspci -vvv for the graphics card: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV350 [Radeon 9550] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 932a Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in “xserver-xorg-video-ati” package in Ubuntu: New Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1325940/+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 1325940] [NEW] Desktop sometimes comes up with undisplayable screen resolution
Public bug reported: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver- xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jun 3 13:23:38 2014 InstallationDate: Installed on 2014-04-22 (41 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "TTY-distorted.ogg" https://bugs.launchpad.net/bugs/1325940/+attachment/4124733/+files/TTY-distorted.ogg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1325940 Title: Desktop sometimes comes up with undisplayable screen resolution Status in “xserver-xorg-video-ati” package in Ubuntu: New Bug description: Hello, the PC from which I'm sending this report sometimes fails to boot into the desktop properly (which desktop environment doesn't seem to matter). In the failure case the following happens: - The Plymouth Ubuntu splash gets displayed, but it looks distorted. Flickering horizontal artifacts are shown all over the screen, it looks a bit like a CRT Television with low signal. - When the desktop is loaded (via autologin), one can see short glimpses of its wallpaper, but after a few second the screen becomes black and remains that way. The monitor _does_ seem to receive a signal though. - It is possible to switch to TTYs and to use them, but they show similar artifacts like the Plymouth logo. - If I query the display information on the monitor's OSD when the screen is distorted, it reports a resolution of 1681x1050 or 1683x1050, which is 1-3 pixel bigger than the native horizontal resolution of the 22" LCD screen. Switching between different resolutions via entering 'xrandr --size 1024x768' blindly, followed by 'xrandr --size 1680x1050' brings up the native resolution properly. This does not happen on every boot, only in ~10-15% of the cases. I was not able to find any pattern so far in the occurence of this bug. The only thing I observed is that it _never_ happens when Windows XP is started, thus my assumption is that the bug is related to the xserver-xorg-video-radeon driver. I tried to specify the correct resolution explicitly on the kernel command line(adding video=DVI-I-1:1680x1050 ) but this has no positive effect. The monitor is connected via DVI. Below is a video attached that tries to show how the TTYs look when this bug occurs. Notice the abnormal blue lines, which are constantly flickering. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture:
[Desktop-packages] [Bug 1240957] Re: Scrolling behaviour and window focus has changed and is inconsistent
@Christopher The Compiz update for Trusty fixes the bug for me, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1240957 Title: Scrolling behaviour and window focus has changed and is inconsistent Status in Compiz: Fix Committed Status in GTK+ GUI Toolkit: Fix Released Status in X.Org X server: Confirmed Status in “compiz” package in Ubuntu: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Won't Fix Bug description: I wasn't sure which package to file this bug against, but seeing as it's a general desktop usability/consistency bug, the top level desktop environment seemed like a good target. On Ubuntu 13.10, AMD64, everything default (Unity 7 on X.org etc), except for installing nvidia-319-updates, all current packages as of now (2013-10-17; unity 7.1.2+13.10.20131014.1-0ubuntu1), I now have this behaviour which is different from Ubuntu versions up to 13.04, and, is also inconsistent within itself. Here's what I've found: The scrolling behaviour has changed, and seems to be different per application in Ubuntu 13.10. The old behaviour (up to 13.04): mouse pointer above window would allow scrolling, regardless of focus Apps that use the old behaviour: libreoffice, firefox, gnome-terminal The new behaviour (13.10): window must be focused, and pointer hovered above to allow scrolling Apps that use the new behaviour: nautilus, gedit, ubuntu-bug, software-updater STEPS TO REPRODUCE 1. Open gEdit, press enter until the window is scrollable. 2. Open Firefox, go to a webpage that's scrollable. 3. Place gEdit above Firefox but off to the right side so gEdit's scrollbar is still visible, have gEdit focused. 4. Position mouse pointer above gEdit, observe scrollwheel causes gEdit window to scroll. 5. Move mouse pointer above Firefox but do not focus Firefox, observe scrollwheel causes Firefox window to scroll. 6. Focus Firefox, leave pointer above Firefox, observe scrollwheel causes Firefox window to scroll 7. Move mouse pointer above gEdit but do not focus gEdit, observe scrollwheel FAILS to cause gEdit window to scroll. This behaviour is the same with any combination of the above apps (libreoffice, firefox, gnome-terminal all scrollable as long as pointer is above them; nautilus, gedit, software-updater, ubunut-bug will not scroll unless focused *and* have pointer above them) What *SHOULD* happen, is that any window will scroll as long as the pointer is above it. That's how it's always been in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 17 22:12:18 2013 InstallationDate: Installed on 2013-09-30 (17 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1240957/+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 1297799] Re: Live image boots into black screen
Couldn't reproduce the bug anymore with today's daily image (20140330), so it might have been fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1297799 Title: Live image boots into black screen Status in Light Display Manager: New Status in Ubuntu Kylin: New Status in “lightdm” package in Ubuntu: Triaged Bug description: Today I tried to do a test installation of Trusty with the current daily live image (via USB stick), but it booted into a black screen after the Plymouth boot animation (the Ubuntu lettering + logo) was shown. The last thing I see during the boot is a short appearence of a mouse cursor, but then everything stays blank (usually an Ubiquity window would appear here to let me choose language and between installing ubuntu or trying out the live image). This behaviour is reproducible. If the screen is black, switching to VTs via Ctr + Alt + F1-F6 works and VTs are usable. I can workaround the black screen if I press F2 early during boot and choose "Try Ubuntu without installing". Then the desktop comes up properly (and I am sending this report from a live image started this way). The last image I used to do a test installation was 20140309, where this bug was absent. I am not sure if Lightdm is actually responsible for the bug, but it seemed to be the best package choice for this bug because the bug occurs when Lightdm should come up. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.13-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CasperVersion: 1.339 CurrentDesktop: Unity Date: Wed Mar 26 10:59:04 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140325.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1297799/+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 1297799] [NEW] Live image boots into black screen
Public bug reported: Today I tried to do a test installation of Trusty with the current daily live image (via USB stick), but it booted into a black screen after the Plymouth boot animation (the Ubuntu lettering + logo) was shown. The last thing I see during the boot is a short appearence of a mouse cursor, but then everything stays blank (usually an Ubiquity window would appear here to let me choose language and between installing ubuntu or trying out the live image). This behaviour is reproducible. If the screen is black, switching to VTs via Ctr + Alt + F1-F6 works and VTs are usable. I can workaround the black screen if I press F2 early during boot and choose "Try Ubuntu without installing". Then the desktop comes up properly (and I am sending this report from a live image started this way). The last image I used to do a test installation was 20140309, where this bug was absent. I am not sure if Lightdm is actually responsible for the bug, but it seemed to be the best package choice for this bug because the bug occurs when Lightdm should come up. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.13-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CasperVersion: 1.339 CurrentDesktop: Unity Date: Wed Mar 26 10:59:04 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140325.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1297799 Title: Live image boots into black screen Status in “lightdm” package in Ubuntu: New Bug description: Today I tried to do a test installation of Trusty with the current daily live image (via USB stick), but it booted into a black screen after the Plymouth boot animation (the Ubuntu lettering + logo) was shown. The last thing I see during the boot is a short appearence of a mouse cursor, but then everything stays blank (usually an Ubiquity window would appear here to let me choose language and between installing ubuntu or trying out the live image). This behaviour is reproducible. If the screen is black, switching to VTs via Ctr + Alt + F1-F6 works and VTs are usable. I can workaround the black screen if I press F2 early during boot and choose "Try Ubuntu without installing". Then the desktop comes up properly (and I am sending this report from a live image started this way). The last image I used to do a test installation was 20140309, where this bug was absent. I am not sure if Lightdm is actually responsible for the bug, but it seemed to be the best package choice for this bug because the bug occurs when Lightdm should come up. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.13-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CasperVersion: 1.339 CurrentDesktop: Unity Date: Wed Mar 26 10:59:04 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140325.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1297799/+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 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)
I have also added a message to the PPA that affected users should use the package updates from saucy-proposed instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1217230 Title: [Regression] Can't copy files from digital camera (Operation not supported by backend) Status in GVFS: Invalid Status in “glib2.0” package in Ubuntu: In Progress Status in “glib2.0” source package in Saucy: Confirmed Status in “glib2.0” source package in Trusty: In Progress Status in “gvfs” package in Debian: Fix Released Status in “gvfs” package in Fedora: Unknown Bug description: [ Description ] Copying from some devices is broken over gvfs [ Test case ] - browse a directory with a .tar.gz, using nautilus - right click on the file, select "open with archive mounter" -> that makes the archive being listed as a mount in the sidebar/unity launcher - browse that mount, find a file to copy in there - try to copy it to your user directory -> if the fix is doing its job, the copy should work without error [ Proposed fix ] Cherry-pick upstream commit 44edc3829d6db3fabe22d837eaaf2638003516c9 to fall back to g_file_query_info if query_info_on_read isn't supported. [ Regression potential ] Adds an extra step into file copying over gvfs. Check all previous gvfs copies still work. [ Original report ] Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. It also works if I copy files with cp in a terminal from gvfs- mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1217230/+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 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)
The glib version 2.38.1-0ubuntu1 that has been uploaded to saucy- proposed fixes the bug for me, many thanks to the uploaders! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1217230 Title: [Regression] Can't copy files from digital camera (Operation not supported by backend) Status in GVFS: Invalid Status in “glib2.0” package in Ubuntu: In Progress Status in “glib2.0” source package in Saucy: Confirmed Status in “glib2.0” source package in Trusty: In Progress Status in “gvfs” package in Debian: Fix Released Status in “gvfs” package in Fedora: Unknown Bug description: [ Description ] Copying from some devices is broken over gvfs [ Test case ] - browse a directory with a .tar.gz, using nautilus - right click on the file, select "open with archive mounter" -> that makes the archive being listed as a mount in the sidebar/unity launcher - browse that mount, find a file to copy in there - try to copy it to your user directory -> if the fix is doing its job, the copy should work without error [ Proposed fix ] Cherry-pick upstream commit 44edc3829d6db3fabe22d837eaaf2638003516c9 to fall back to g_file_query_info if query_info_on_read isn't supported. [ Regression potential ] Adds an extra step into file copying over gvfs. Check all previous gvfs copies still work. [ Original report ] Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. It also works if I copy files with cp in a terminal from gvfs- mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1217230/+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 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)
PPA for testing the upstream patch is ready: https://launchpad.net/~kaiserclaudius/+archive/glib2.0bugfixtest -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1217230 Title: [Regression] Can't copy files from digital camera (Operation not supported by backend) Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Status in “gvfs” package in Debian: New Status in “gvfs” package in Fedora: Unknown Bug description: Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. It also works if I copy files with cp in a terminal from gvfs- mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1217230/+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 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)
A patch from upstream (for glib2.0) has recently been posted here: https://bugzilla.gnome.org/show_bug.cgi?id=706254#c12 I have build a new libglib2-version with this patch applied, and it seems to fix the bug for me. I am preparing a PPA with the updated packages, so others can also test the fix easily. Kind regards, Jan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1217230 Title: [Regression] Can't copy files from digital camera (Operation not supported by backend) Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Status in “gvfs” package in Debian: New Status in “gvfs” package in Fedora: Unknown Bug description: Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. It also works if I copy files with cp in a terminal from gvfs- mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1217230/+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 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)
@Hotteterre Upstream bug report https://bugzilla.gnome.org/show_bug.cgi?id=706254 hints the assumption that this bug is not depended on any particular gvfs protocol. So I would assume at the moment that your bug is another manisfestation of the bug reported here, thus it is not necessary to create a separate report. ** Bug watch added: GNOME Bug Tracker #706254 https://bugzilla.gnome.org/show_bug.cgi?id=706254 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1217230 Title: [Regression] Can't copy files from digital camera (Operation not supported by backend) Status in GVFS: New Status in “gvfs” package in Ubuntu: Confirmed Status in “gvfs” package in Debian: New Status in “gvfs” package in Fedora: Unknown Bug description: Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. It also works if I copy files with cp in a terminal from gvfs- mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1217230/+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 1010794] Re: Graphics/text corruptions in some applications with nouveau drivers
Hello Steve, I'm a bit confused, from my point of view the fix for this bug has been in Quantal since end of last November, and I had verified the fix at that time (see comments 191 - 193). Also testing again would be a bit hard since I'm on Raring since its release and I currently don't have a partition with Quantal on my system anymore. However, if it is really necessary, I could try to test with booting from an USB stick and selectively installing the respective updates. Kind regards, Jan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1010794 Title: Graphics/text corruptions in some applications with nouveau drivers Status in Accelerated Xorg driver for nVidia cards: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xserver-xorg-video-nouveau” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Fix Released Status in “xserver-xorg-video-nouveau” source package in Precise: Invalid Status in “xorg-server” source package in Quantal: Fix Released Status in “xserver-xorg-video-nouveau” source package in Quantal: Fix Committed Status in “xorg-server” source package in Raring: Fix Released Status in “xserver-xorg-video-nouveau” source package in Raring: Fix Released Bug description: For xserver-xorg-video-nouveau sru: [IMPACT] * Enables SolidFill on fermi and kepler cards, increasing performance slightly. [TESTCASE] * start ubuntu software center * hover over some urls and icons, likely corruption already occurs at this point, the more you mover over the more it shows. * This wil not fix it completely, only make it occur less, see xorg-server below for the real fix. [Regression Potential] * This should be a safe fix, since it simply enables some code which was already created specifically for these cards, and with some testing it appears to work just fine. * I expect no regressions, but in the worst case this would result in garbage being sent to the card, which may cause it to do an unexplained hang or (more likely) errors in dmesg and worse glitches since nothing is being shown any more. [Other Info] * Doing solid fill in hardware is a pretty nice speedup for those who use valgrind to test code, and also seems to increase responsitivity a little on nouveau without valgrind, since it safes 2 memcpy's on host, 2 memcpy's on gpu, and a memset. For the xorg-server sru: [IMPACT] * Fallback to exa with gradients and solid pictures results in visual corruption, because sometimes the source or mark pixmaps from previous operations are used. This results in visual corruption when those fallbacks are triggered. The xxv-nouveau fix helps slightly because it disables fallback for solid fills, but gradients are still not handled so it still triggers it. [TESTCASE] * Start ubuntu software center on a geforce card that has exa acceleration enabled. * Highlight mouse over items * Notice display corruption. [Regression Potential] * The patch has been reviewed by upstream, but is not yet included (upstream can be slow). The most likely regression would be that suddenly other operations start failing to draw correctly, or worst case cause crashes but I do not think it is likely. [Other Info] See also http://www.mail-archive.com/xorg-devel@lists.x.org/msg33376.html [Original bug report] Hello, there are several serious graphic and text corruptions on Quantal with nouveau drivers (which are used by default). To reproduce: - Boot a Quantal live system or a fresh installation - Start software-center. - Move the mouse in its window or click anything. Result: Text and some graphics become massively corrupted (See also attached screenshots and short demo video). I have seen this kind of corruption so far in software-center, ubiquity-slideshow (during installation) and one time on filename text field of gtk-filechooser. Booting the system with "nomodeset" seems to make the problem go away, as well as installing the propritary Nvidia drivers. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.1.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 14.977209] [drm] nouveau :01:00.0: PMFB0_SUBP0: 0x037f0040 [ 14.977214] [drm] nouveau :01:00.0: PMFB0_SUBP1: 0x037f [ 22.821303] [drm] nouveau :01:00.0: PFIFO: unknown status 0x4000 [ 22.920011] eth0: no IPv6 routers present Date: Sat Jun 9 09:
[Desktop-packages] [Bug 1217230] Re: [Regression] Can't copy files from digital camera (Operation not supported by backend)
According to bug reports in Debian and Fedora this is a Gvfs bug, so I reassign the bug to that package. ** Package changed: libgphoto2 (Ubuntu) => gvfs (Ubuntu) ** Bug watch added: Debian Bug tracker #715436 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715436 ** Also affects: gvfs (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715436 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #984913 https://bugzilla.redhat.com/show_bug.cgi?id=984913 ** Also affects: gvfs (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=984913 Importance: Unknown Status: Unknown ** Tags added: apport-collected ** Description changed: Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.12.1-0ubuntu3 + Architecture: amd64 + DistroRelease: Ubuntu 13.10 + InstallationDate: Installed on 2013-08-02 (34 days ago) + InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) + MarkForUpload: True + Package: gvfs 1.17.90-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 + Tags: saucy + Uname: Linux 3.11.0-4-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1217230 Title: [Regression] Can't copy files from digital camera (Operation not supported by backend) Status in “gvfs” package in Ubuntu: New Status in “gvfs” package in Debian: Unknown Status in “gvfs” package in Fedora: Unknown Bug description: Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. It also works if I copy files with cp in a terminal from gvfs- mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1217230] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1217230/+attachment/3805468/+files/ProcEnviron.txt ** Description changed: Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. + It also works if I copy files with cp in a terminal from gvfs-mountpoint + mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . + Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) - --- + --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1217230 Title: [Regression] Can't copy files from digital camera (Operation not supported by backend) Status in “gvfs” package in Ubuntu: New Status in “gvfs” package in Debian: Unknown Status in “gvfs” package in Fedora: Unknown Bug description: Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. It also works if I copy files with cp in a terminal from gvfs- mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1217230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1217230] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1217230/+attachment/3805467/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1217230 Title: [Regression] Can't copy files from digital camera (Operation not supported by backend) Status in “gvfs” package in Ubuntu: New Status in “gvfs” package in Debian: Unknown Status in “gvfs” package in Fedora: Unknown Bug description: Hello, on Saucy I can't copy files from my digital camera to my PC anymore via file manager. This is a serious regression since it worked on all previous version of Ubuntu since Lucid at least (even earlier versions not tested because I didn't own the camera at that time). It is easy to reproduce: - Start PC from USB stick with current Saucy daily live image - Connect and turn on camera - Open Nautilus, browse the files on the camera, select one of them and right-click -> copy - Now when I try to paste the file into my home directory, I get an error dialog saying copying failed with the reason "Operation not supported by backend" (see attached screenshot) I get the same error message if I try to copy the file on terminal with the command gvfs-copy. However, if I try to copy a file on terminal with the gphoto2 tool, e.g. 'gphoto2 --get-file 1', this works. It also works if I copy files with cp in a terminal from gvfs- mountpoint mounted at /run/user/my_userid/gvfs/my_camera_mountpoint . Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgphoto2-6 2.5.2-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:18:22 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libgphoto2 UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2013-08-02 (34 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130802) MarkForUpload: True Package: gvfs 1.17.90-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Tags: saucy Uname: Linux 3.11.0-4-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1217230/+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 1217233] [NEW] Can't do 2-pass video encoding to webm
Public bug reported: Hello, it is currently not possible encode video files to WebM with avconv with 2-pass encoding. The first pass succeeds, but on the second avconv failes with an error message like: [webm @ 0x24ca040] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 33 >= 33 av_interleaved_write_frame(): Invalid argument (See attached file for full log of both avconv commands) This seems to happen with input files in arbitrary formats. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libav-tools 6:0.8.7-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:47:49 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libav UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libav (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: "Output of the two avconv commands" https://bugs.launchpad.net/bugs/1217233/+attachment/3789583/+files/avconv.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1217233 Title: Can't do 2-pass video encoding to webm Status in “libav” package in Ubuntu: New Bug description: Hello, it is currently not possible encode video files to WebM with avconv with 2-pass encoding. The first pass succeeds, but on the second avconv failes with an error message like: [webm @ 0x24ca040] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 33 >= 33 av_interleaved_write_frame(): Invalid argument (See attached file for full log of both avconv commands) This seems to happen with input files in arbitrary formats. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libav-tools 6:0.8.7-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:47:49 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libav UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1217233/+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 1217233] Re: Can't do 2-pass video encoding to webm
I'm also attaching the avpreset file I use. ** Attachment added: "libvpx-canon.avpreset" https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1217233/+attachment/3789586/+files/libvpx-canon.avpreset -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1217233 Title: Can't do 2-pass video encoding to webm Status in “libav” package in Ubuntu: New Bug description: Hello, it is currently not possible encode video files to WebM with avconv with 2-pass encoding. The first pass succeeds, but on the second avconv failes with an error message like: [webm @ 0x24ca040] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 33 >= 33 av_interleaved_write_frame(): Invalid argument (See attached file for full log of both avconv commands) This seems to happen with input files in arbitrary formats. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libav-tools 6:0.8.7-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.336 Date: Tue Aug 27 07:47:49 2013 LiveMediaBuild: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130826) MarkForUpload: True SourcePackage: libav UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1217233/+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 1168708] Re: Noveau driver isn't loaded anymore since kernel 3.2.0-39
I have just tested the lastet version of the 3.2 kernel and Nouveau is working properly again, so at least for me this problem is fixed. Kind regards, Jan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1168708 Title: Noveau driver isn't loaded anymore since kernel 3.2.0-39 Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Hello, on this machine, since the newest kernel updates the Nouveau driver doesn't get loaded anymore (the graphic card is a Geforce 2 MX). The unfortunate consequence is that the screen resolution is limited to 1024x768. The last kernel version where the Nouveau driver works is 3.2.0-38 . If I run 3.2.0-39, 3.2.0-40 or the Quantal kernel 3.5.x, the Nouveau kernel modules are obviously not loaded during boot (the output of 'lsmod | grep nouveau' is empty). If I inspect the log files like /var/log/kern.log or /var/log/dmesg, I can't find any reference to the Nouveau driver and no possible hints why it wasn't loaded. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic-pae 3.2.40 Uname: Linux 3.2.0-40-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Apr 13 19:17:05 2013 DistUpgraded: 2012-09-09 13:25:23,873 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: NVIDIA Corporation NV11 [GeForce2 MX/MX 400] [10de:0110] (rev b2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. AGP-V7100 Pro [1043:4015] MarkForUpload: True PlymouthDebug: Error: [Errno 13] Keine Berechtigung: '/var/log/plymouth-debug.log' ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-40-generic-pae root=UUID=21f9d629-6568-4a6b-9b16-6b51bcaa1693 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to precise on 2012-09-09 (216 days ago) dmi.modalias: dmi: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.39-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.12 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1168708/+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 1207848] Re: NetworkManager doesn't quit properly on shutdown
** Summary changed: - Shutdown takes an unusual amount of time + NetworkManager doesn't quit properly on shutdown -- 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/1207848 Title: NetworkManager doesn't quit properly on shutdown Status in “network-manager” package in Ubuntu: New Bug description: Hello, my system takes a rather long time to shutdown (~7-10 sec.) while there are often error messages flashing on the screen like: - Killing all remaining processes failed - Mount: / is busy To investigate the problem, I patched my /etc/init.d/umountfs and umountroot scripts with the proposed changes from https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log- processes-and-open-files-on-shutdown/+merge/163740 to log open files at shutdown and attached the resulting shutdown-lsof.log here. The only thing in that log that looks suspicious to me are the ones regarding dhclient: dhclient 578610 cwdDIR 252,5 4096 2 / dhclient 578610 rtdDIR 252,5 4096 2 / dhclient 578610 txtREG 252,5 1659968 654751 /sbin/dhclient dhclient 578610 memREG 252,552168 786517 /lib/x86_64-linux-gnu/libnss_files-2.17.so dhclient 578610 memREG 252,5 1848024 786477 /lib/x86_64-linux-gnu/libc-2.17.so dhclient 578610 memREG 252,5 149312 786464 /lib/x86_64-linux-gnu/ld-2.17.so dhclient 5786104w REG 252,5 1058 21443 /var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease Maybe there is some problem shutting down NetworkManager? I found the respective dhclient entries on two separate shutdown logs. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Fri Aug 2 19:30:06 2013 InstallationDate: Installed on 2013-04-10 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=/dev/mapper/internal--ssd-root ro quiet SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/at.deny'] --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 DistroRelease: Ubuntu 13.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-10 (116 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.21 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.8.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 RfKill: Tags: raring Uname: Linux 3.8.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 2012-04-12T20:53:51 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto-Ethernet 8f9a3dff-24e6-4374-b0b2-c38524cdc0ce 802-3-ethernet1375699766 Mo 05 Aug 2013 12:49:26 CEST yes no /org/freedesktop/NetworkManager/Settings/2 Xag56Rs#xP38d171a1-ae74-449a-ab52-39274a4dfb60 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 HS-Fulda-VPN 44ed749b-56b2-42eb-8717-08e5e0ef49a6 vpn 1375200591 Di 30 Jul 2013 18:09:51 CEST yes no /org/free
[Desktop-packages] [Bug 1084960] Re: 10de:0de1 [GeForce GT 430] Resume from Standby mode doesn't work with Nouveau
@Christopher BIOS update is a risky operation that I would rather like to avoid. In addition, the only change noted for that particular update is "Support Xpress BIOS Rescue function", so it seems to me that this update will just add that described functionality and not fix any possible bugs (at least there is no hint that it contains any bugfixes) and thus could not have any positive effect on this bug. My current output of "sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date" is: F13 07/10/2008 Kind regards, Jan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1084960 Title: 10de:0de1 [GeForce GT 430] Resume from Standby mode doesn't work with Nouveau Status in “linux” package in Ubuntu: Incomplete Status in “xserver-xorg-video-nouveau” package in Ubuntu: Triaged Bug description: Hello, if I'm using the Nouveau driver with my graphics board (Geforce GT430), standby mode (a.k.a. suspend-to-ram) does not work. Going into standby mode itself works, but when I turn my PC back on, the monitor shows just a kind of colorful "noise" with the usual mouse cursor (the cursor itself is displayed properly). Sometimes it's possible to move the cursor a bit, but the system can't be used anymore and has to rebooted with the Alt+Print+b keycombo. This also happens on Quantal when I use the Nouveau driver. WORKAROUND: The propritary Nvidia driver works fine. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6 Uname: Linux 3.7.0-3-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Nov 30 10:34:21 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2012-11-26 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-3-generic root=/dev/mapper/internal--hdd-test1 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.40-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.14-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Fri Nov 30 10:33:12 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Laser Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.0-0ubuntu8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1084960/+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 1207848] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1207848/+attachment/3761208/+files/ProcEnviron.txt -- 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/1207848 Title: Shutdown takes an unusual amount of time Status in “network-manager” package in Ubuntu: New Bug description: Hello, my system takes a rather long time to shutdown (~7-10 sec.) while there are often error messages flashing on the screen like: - Killing all remaining processes failed - Mount: / is busy To investigate the problem, I patched my /etc/init.d/umountfs and umountroot scripts with the proposed changes from https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log- processes-and-open-files-on-shutdown/+merge/163740 to log open files at shutdown and attached the resulting shutdown-lsof.log here. The only thing in that log that looks suspicious to me are the ones regarding dhclient: dhclient 578610 cwdDIR 252,5 4096 2 / dhclient 578610 rtdDIR 252,5 4096 2 / dhclient 578610 txtREG 252,5 1659968 654751 /sbin/dhclient dhclient 578610 memREG 252,552168 786517 /lib/x86_64-linux-gnu/libnss_files-2.17.so dhclient 578610 memREG 252,5 1848024 786477 /lib/x86_64-linux-gnu/libc-2.17.so dhclient 578610 memREG 252,5 149312 786464 /lib/x86_64-linux-gnu/ld-2.17.so dhclient 5786104w REG 252,5 1058 21443 /var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease Maybe there is some problem shutting down NetworkManager? I found the respective dhclient entries on two separate shutdown logs. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Fri Aug 2 19:30:06 2013 InstallationDate: Installed on 2013-04-10 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=/dev/mapper/internal--ssd-root ro quiet SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/at.deny'] --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 DistroRelease: Ubuntu 13.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-10 (116 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.21 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.8.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 RfKill: Tags: raring Uname: Linux 3.8.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 2012-04-12T20:53:51 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto-Ethernet 8f9a3dff-24e6-4374-b0b2-c38524cdc0ce 802-3-ethernet1375699766 Mo 05 Aug 2013 12:49:26 CEST yes no /org/freedesktop/NetworkManager/Settings/2 Xag56Rs#xP38d171a1-ae74-449a-ab52-39274a4dfb60 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 HS-Fulda-VPN 44ed749b-56b2-42eb-8717-08e5e0ef49a6 vpn 1375200591 Di 30 Jul 2013 18:09:51 CEST yes
[Desktop-packages] [Bug 1207848] NetDevice.eth0.txt
apport information ** Attachment added: "NetDevice.eth0.txt" https://bugs.launchpad.net/bugs/1207848/+attachment/3761204/+files/NetDevice.eth0.txt -- 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/1207848 Title: Shutdown takes an unusual amount of time Status in “network-manager” package in Ubuntu: New Bug description: Hello, my system takes a rather long time to shutdown (~7-10 sec.) while there are often error messages flashing on the screen like: - Killing all remaining processes failed - Mount: / is busy To investigate the problem, I patched my /etc/init.d/umountfs and umountroot scripts with the proposed changes from https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log- processes-and-open-files-on-shutdown/+merge/163740 to log open files at shutdown and attached the resulting shutdown-lsof.log here. The only thing in that log that looks suspicious to me are the ones regarding dhclient: dhclient 578610 cwdDIR 252,5 4096 2 / dhclient 578610 rtdDIR 252,5 4096 2 / dhclient 578610 txtREG 252,5 1659968 654751 /sbin/dhclient dhclient 578610 memREG 252,552168 786517 /lib/x86_64-linux-gnu/libnss_files-2.17.so dhclient 578610 memREG 252,5 1848024 786477 /lib/x86_64-linux-gnu/libc-2.17.so dhclient 578610 memREG 252,5 149312 786464 /lib/x86_64-linux-gnu/ld-2.17.so dhclient 5786104w REG 252,5 1058 21443 /var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease Maybe there is some problem shutting down NetworkManager? I found the respective dhclient entries on two separate shutdown logs. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Fri Aug 2 19:30:06 2013 InstallationDate: Installed on 2013-04-10 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=/dev/mapper/internal--ssd-root ro quiet SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/at.deny'] --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 DistroRelease: Ubuntu 13.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-10 (116 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.21 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.8.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 RfKill: Tags: raring Uname: Linux 3.8.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 2012-04-12T20:53:51 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto-Ethernet 8f9a3dff-24e6-4374-b0b2-c38524cdc0ce 802-3-ethernet1375699766 Mo 05 Aug 2013 12:49:26 CEST yes no /org/freedesktop/NetworkManager/Settings/2 Xag56Rs#xP38d171a1-ae74-449a-ab52-39274a4dfb60 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 HS-Fulda-VPN 44ed749b-56b2-42eb-8717-08e5e0ef49a6 vpn 1375200591 Di 30 Jul 2013 18:09:51 CEST yes
[Desktop-packages] [Bug 1207848] Re: Shutdown takes an unusual amount of time
Since the bug was reassigned to NetworkManager, I have run apport- collect to attach relevant files regarding NetworkManager. Kind regards, Jan -- 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/1207848 Title: Shutdown takes an unusual amount of time Status in “network-manager” package in Ubuntu: New Bug description: Hello, my system takes a rather long time to shutdown (~7-10 sec.) while there are often error messages flashing on the screen like: - Killing all remaining processes failed - Mount: / is busy To investigate the problem, I patched my /etc/init.d/umountfs and umountroot scripts with the proposed changes from https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log- processes-and-open-files-on-shutdown/+merge/163740 to log open files at shutdown and attached the resulting shutdown-lsof.log here. The only thing in that log that looks suspicious to me are the ones regarding dhclient: dhclient 578610 cwdDIR 252,5 4096 2 / dhclient 578610 rtdDIR 252,5 4096 2 / dhclient 578610 txtREG 252,5 1659968 654751 /sbin/dhclient dhclient 578610 memREG 252,552168 786517 /lib/x86_64-linux-gnu/libnss_files-2.17.so dhclient 578610 memREG 252,5 1848024 786477 /lib/x86_64-linux-gnu/libc-2.17.so dhclient 578610 memREG 252,5 149312 786464 /lib/x86_64-linux-gnu/ld-2.17.so dhclient 5786104w REG 252,5 1058 21443 /var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease Maybe there is some problem shutting down NetworkManager? I found the respective dhclient entries on two separate shutdown logs. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Fri Aug 2 19:30:06 2013 InstallationDate: Installed on 2013-04-10 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=/dev/mapper/internal--ssd-root ro quiet SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/at.deny'] --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 DistroRelease: Ubuntu 13.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-10 (116 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.21 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.8.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 RfKill: Tags: raring Uname: Linux 3.8.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 2012-04-12T20:53:51 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto-Ethernet 8f9a3dff-24e6-4374-b0b2-c38524cdc0ce 802-3-ethernet1375699766 Mo 05 Aug 2013 12:49:26 CEST yes no /org/freedesktop/NetworkManager/Settings/2 Xag56Rs#xP38d171a1-ae74-449a-ab52-39274a4dfb60 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 HS-Fulda-VPN 44ed749b-56b2-42eb-8717-08e5e0ef49a6 vpn 1375200591 Di 30 Jul 2013 18:09:51 CEST yes
[Desktop-packages] [Bug 1207848] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1207848/+attachment/3761205/+files/NetDevice.lo.txt -- 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/1207848 Title: Shutdown takes an unusual amount of time Status in “network-manager” package in Ubuntu: New Bug description: Hello, my system takes a rather long time to shutdown (~7-10 sec.) while there are often error messages flashing on the screen like: - Killing all remaining processes failed - Mount: / is busy To investigate the problem, I patched my /etc/init.d/umountfs and umountroot scripts with the proposed changes from https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log- processes-and-open-files-on-shutdown/+merge/163740 to log open files at shutdown and attached the resulting shutdown-lsof.log here. The only thing in that log that looks suspicious to me are the ones regarding dhclient: dhclient 578610 cwdDIR 252,5 4096 2 / dhclient 578610 rtdDIR 252,5 4096 2 / dhclient 578610 txtREG 252,5 1659968 654751 /sbin/dhclient dhclient 578610 memREG 252,552168 786517 /lib/x86_64-linux-gnu/libnss_files-2.17.so dhclient 578610 memREG 252,5 1848024 786477 /lib/x86_64-linux-gnu/libc-2.17.so dhclient 578610 memREG 252,5 149312 786464 /lib/x86_64-linux-gnu/ld-2.17.so dhclient 5786104w REG 252,5 1058 21443 /var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease Maybe there is some problem shutting down NetworkManager? I found the respective dhclient entries on two separate shutdown logs. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Fri Aug 2 19:30:06 2013 InstallationDate: Installed on 2013-04-10 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=/dev/mapper/internal--ssd-root ro quiet SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/at.deny'] --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 DistroRelease: Ubuntu 13.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-10 (116 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.21 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.8.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 RfKill: Tags: raring Uname: Linux 3.8.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 2012-04-12T20:53:51 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto-Ethernet 8f9a3dff-24e6-4374-b0b2-c38524cdc0ce 802-3-ethernet1375699766 Mo 05 Aug 2013 12:49:26 CEST yes no /org/freedesktop/NetworkManager/Settings/2 Xag56Rs#xP38d171a1-ae74-449a-ab52-39274a4dfb60 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 HS-Fulda-VPN 44ed749b-56b2-42eb-8717-08e5e0ef49a6 vpn 1375200591 Di 30 Jul 2013 18:09:51 CEST yes
[Desktop-packages] [Bug 1207848] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1207848/+attachment/3761206/+files/NetworkManager.conf.txt -- 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/1207848 Title: Shutdown takes an unusual amount of time Status in “network-manager” package in Ubuntu: New Bug description: Hello, my system takes a rather long time to shutdown (~7-10 sec.) while there are often error messages flashing on the screen like: - Killing all remaining processes failed - Mount: / is busy To investigate the problem, I patched my /etc/init.d/umountfs and umountroot scripts with the proposed changes from https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log- processes-and-open-files-on-shutdown/+merge/163740 to log open files at shutdown and attached the resulting shutdown-lsof.log here. The only thing in that log that looks suspicious to me are the ones regarding dhclient: dhclient 578610 cwdDIR 252,5 4096 2 / dhclient 578610 rtdDIR 252,5 4096 2 / dhclient 578610 txtREG 252,5 1659968 654751 /sbin/dhclient dhclient 578610 memREG 252,552168 786517 /lib/x86_64-linux-gnu/libnss_files-2.17.so dhclient 578610 memREG 252,5 1848024 786477 /lib/x86_64-linux-gnu/libc-2.17.so dhclient 578610 memREG 252,5 149312 786464 /lib/x86_64-linux-gnu/ld-2.17.so dhclient 5786104w REG 252,5 1058 21443 /var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease Maybe there is some problem shutting down NetworkManager? I found the respective dhclient entries on two separate shutdown logs. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Fri Aug 2 19:30:06 2013 InstallationDate: Installed on 2013-04-10 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=/dev/mapper/internal--ssd-root ro quiet SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/at.deny'] --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 DistroRelease: Ubuntu 13.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-10 (116 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.21 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.8.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 RfKill: Tags: raring Uname: Linux 3.8.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 2012-04-12T20:53:51 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto-Ethernet 8f9a3dff-24e6-4374-b0b2-c38524cdc0ce 802-3-ethernet1375699766 Mo 05 Aug 2013 12:49:26 CEST yes no /org/freedesktop/NetworkManager/Settings/2 Xag56Rs#xP38d171a1-ae74-449a-ab52-39274a4dfb60 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 HS-Fulda-VPN 44ed749b-56b2-42eb-8717-08e5e0ef49a6 vpn 1375200591 Di 30 Jul 2013 18:09:51 CEST
[Desktop-packages] [Bug 1207848] modified.conffile..etc.NetworkManager.dispatcher.d.01ifupdown.txt
apport information ** Attachment added: "modified.conffile..etc.NetworkManager.dispatcher.d.01ifupdown.txt" https://bugs.launchpad.net/bugs/1207848/+attachment/3761210/+files/modified.conffile..etc.NetworkManager.dispatcher.d.01ifupdown.txt -- 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/1207848 Title: Shutdown takes an unusual amount of time Status in “network-manager” package in Ubuntu: New Bug description: Hello, my system takes a rather long time to shutdown (~7-10 sec.) while there are often error messages flashing on the screen like: - Killing all remaining processes failed - Mount: / is busy To investigate the problem, I patched my /etc/init.d/umountfs and umountroot scripts with the proposed changes from https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log- processes-and-open-files-on-shutdown/+merge/163740 to log open files at shutdown and attached the resulting shutdown-lsof.log here. The only thing in that log that looks suspicious to me are the ones regarding dhclient: dhclient 578610 cwdDIR 252,5 4096 2 / dhclient 578610 rtdDIR 252,5 4096 2 / dhclient 578610 txtREG 252,5 1659968 654751 /sbin/dhclient dhclient 578610 memREG 252,552168 786517 /lib/x86_64-linux-gnu/libnss_files-2.17.so dhclient 578610 memREG 252,5 1848024 786477 /lib/x86_64-linux-gnu/libc-2.17.so dhclient 578610 memREG 252,5 149312 786464 /lib/x86_64-linux-gnu/ld-2.17.so dhclient 5786104w REG 252,5 1058 21443 /var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease Maybe there is some problem shutting down NetworkManager? I found the respective dhclient entries on two separate shutdown logs. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Fri Aug 2 19:30:06 2013 InstallationDate: Installed on 2013-04-10 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=/dev/mapper/internal--ssd-root ro quiet SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/at.deny'] --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 DistroRelease: Ubuntu 13.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-10 (116 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.21 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.8.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 RfKill: Tags: raring Uname: Linux 3.8.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 2012-04-12T20:53:51 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto-Ethernet 8f9a3dff-24e6-4374-b0b2-c38524cdc0ce 802-3-ethernet1375699766 Mo 05 Aug 2013 12:49:26 CEST yes no /org/freedesktop/NetworkManager/Settings/2 Xag56Rs#xP38d171a1-ae74-449a-ab52-39274a4dfb60 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 HS-Fulda-VPN 44ed749b-56b2-42e
[Desktop-packages] [Bug 1207848] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1207848/+attachment/3761209/+files/WifiSyslog.txt -- 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/1207848 Title: Shutdown takes an unusual amount of time Status in “network-manager” package in Ubuntu: New Bug description: Hello, my system takes a rather long time to shutdown (~7-10 sec.) while there are often error messages flashing on the screen like: - Killing all remaining processes failed - Mount: / is busy To investigate the problem, I patched my /etc/init.d/umountfs and umountroot scripts with the proposed changes from https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log- processes-and-open-files-on-shutdown/+merge/163740 to log open files at shutdown and attached the resulting shutdown-lsof.log here. The only thing in that log that looks suspicious to me are the ones regarding dhclient: dhclient 578610 cwdDIR 252,5 4096 2 / dhclient 578610 rtdDIR 252,5 4096 2 / dhclient 578610 txtREG 252,5 1659968 654751 /sbin/dhclient dhclient 578610 memREG 252,552168 786517 /lib/x86_64-linux-gnu/libnss_files-2.17.so dhclient 578610 memREG 252,5 1848024 786477 /lib/x86_64-linux-gnu/libc-2.17.so dhclient 578610 memREG 252,5 149312 786464 /lib/x86_64-linux-gnu/ld-2.17.so dhclient 5786104w REG 252,5 1058 21443 /var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease Maybe there is some problem shutting down NetworkManager? I found the respective dhclient entries on two separate shutdown logs. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Fri Aug 2 19:30:06 2013 InstallationDate: Installed on 2013-04-10 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=/dev/mapper/internal--ssd-root ro quiet SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/at.deny'] --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 DistroRelease: Ubuntu 13.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-10 (116 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.21 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.8.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 RfKill: Tags: raring Uname: Linux 3.8.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 2012-04-12T20:53:51 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto-Ethernet 8f9a3dff-24e6-4374-b0b2-c38524cdc0ce 802-3-ethernet1375699766 Mo 05 Aug 2013 12:49:26 CEST yes no /org/freedesktop/NetworkManager/Settings/2 Xag56Rs#xP38d171a1-ae74-449a-ab52-39274a4dfb60 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 HS-Fulda-VPN 44ed749b-56b2-42eb-8717-08e5e0ef49a6 vpn 1375200591 Di 30 Jul 2013 18:09:51 CEST yes
[Desktop-packages] [Bug 1207848] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1207848/+attachment/3761203/+files/IpAddr.txt -- 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/1207848 Title: Shutdown takes an unusual amount of time Status in “network-manager” package in Ubuntu: New Bug description: Hello, my system takes a rather long time to shutdown (~7-10 sec.) while there are often error messages flashing on the screen like: - Killing all remaining processes failed - Mount: / is busy To investigate the problem, I patched my /etc/init.d/umountfs and umountroot scripts with the proposed changes from https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log- processes-and-open-files-on-shutdown/+merge/163740 to log open files at shutdown and attached the resulting shutdown-lsof.log here. The only thing in that log that looks suspicious to me are the ones regarding dhclient: dhclient 578610 cwdDIR 252,5 4096 2 / dhclient 578610 rtdDIR 252,5 4096 2 / dhclient 578610 txtREG 252,5 1659968 654751 /sbin/dhclient dhclient 578610 memREG 252,552168 786517 /lib/x86_64-linux-gnu/libnss_files-2.17.so dhclient 578610 memREG 252,5 1848024 786477 /lib/x86_64-linux-gnu/libc-2.17.so dhclient 578610 memREG 252,5 149312 786464 /lib/x86_64-linux-gnu/ld-2.17.so dhclient 5786104w REG 252,5 1058 21443 /var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease Maybe there is some problem shutting down NetworkManager? I found the respective dhclient entries on two separate shutdown logs. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Fri Aug 2 19:30:06 2013 InstallationDate: Installed on 2013-04-10 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=/dev/mapper/internal--ssd-root ro quiet SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/at.deny'] --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 DistroRelease: Ubuntu 13.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-10 (116 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.21 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.8.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 RfKill: Tags: raring Uname: Linux 3.8.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 2012-04-12T20:53:51 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto-Ethernet 8f9a3dff-24e6-4374-b0b2-c38524cdc0ce 802-3-ethernet1375699766 Mo 05 Aug 2013 12:49:26 CEST yes no /org/freedesktop/NetworkManager/Settings/2 Xag56Rs#xP38d171a1-ae74-449a-ab52-39274a4dfb60 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 HS-Fulda-VPN 44ed749b-56b2-42eb-8717-08e5e0ef49a6 vpn 1375200591 Di 30 Jul 2013 18:09:51 CEST yes no
[Desktop-packages] [Bug 1207848] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1207848/+attachment/3761207/+files/PciNetwork.txt -- 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/1207848 Title: Shutdown takes an unusual amount of time Status in “network-manager” package in Ubuntu: New Bug description: Hello, my system takes a rather long time to shutdown (~7-10 sec.) while there are often error messages flashing on the screen like: - Killing all remaining processes failed - Mount: / is busy To investigate the problem, I patched my /etc/init.d/umountfs and umountroot scripts with the proposed changes from https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log- processes-and-open-files-on-shutdown/+merge/163740 to log open files at shutdown and attached the resulting shutdown-lsof.log here. The only thing in that log that looks suspicious to me are the ones regarding dhclient: dhclient 578610 cwdDIR 252,5 4096 2 / dhclient 578610 rtdDIR 252,5 4096 2 / dhclient 578610 txtREG 252,5 1659968 654751 /sbin/dhclient dhclient 578610 memREG 252,552168 786517 /lib/x86_64-linux-gnu/libnss_files-2.17.so dhclient 578610 memREG 252,5 1848024 786477 /lib/x86_64-linux-gnu/libc-2.17.so dhclient 578610 memREG 252,5 149312 786464 /lib/x86_64-linux-gnu/ld-2.17.so dhclient 5786104w REG 252,5 1058 21443 /var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease Maybe there is some problem shutting down NetworkManager? I found the respective dhclient entries on two separate shutdown logs. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Fri Aug 2 19:30:06 2013 InstallationDate: Installed on 2013-04-10 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=/dev/mapper/internal--ssd-root ro quiet SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/at.deny'] --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 DistroRelease: Ubuntu 13.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-10 (116 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) IpRoute: default via 192.168.178.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.21 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true NonfreeKernelModules: nvidia Package: network-manager 0.9.8.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 RfKill: Tags: raring Uname: Linux 3.8.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 2012-04-12T20:53:51 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto-Ethernet 8f9a3dff-24e6-4374-b0b2-c38524cdc0ce 802-3-ethernet1375699766 Mo 05 Aug 2013 12:49:26 CEST yes no /org/freedesktop/NetworkManager/Settings/2 Xag56Rs#xP38d171a1-ae74-449a-ab52-39274a4dfb60 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 HS-Fulda-VPN 44ed749b-56b2-42eb-8717-08e5e0ef49a6 vpn 1375200591 Di 30 Jul 2013 18:09:51 CEST yes
[Desktop-packages] [Bug 1207848] Re: Shutdown takes an unusual amount of time
apport information ** Tags added: apport-collected ** Description changed: Hello, my system takes a rather long time to shutdown (~7-10 sec.) while there are often error messages flashing on the screen like: - Killing all remaining processes failed - Mount: / is busy To investigate the problem, I patched my /etc/init.d/umountfs and umountroot scripts with the proposed changes from https://code.launchpad.net/~jamesodhunt/ubuntu/saucy/sysvinit/log- processes-and-open-files-on-shutdown/+merge/163740 to log open files at shutdown and attached the resulting shutdown-lsof.log here. The only thing in that log that looks suspicious to me are the ones regarding dhclient: dhclient 578610 cwdDIR 252,5 4096 2 / dhclient 578610 rtdDIR 252,5 4096 2 / dhclient 578610 txtREG 252,5 1659968 654751 /sbin/dhclient dhclient 578610 memREG 252,552168 786517 /lib/x86_64-linux-gnu/libnss_files-2.17.so dhclient 578610 memREG 252,5 1848024 786477 /lib/x86_64-linux-gnu/libc-2.17.so dhclient 578610 memREG 252,5 149312 786464 /lib/x86_64-linux-gnu/ld-2.17.so dhclient 5786104w REG 252,5 1058 21443 /var/lib/NetworkManager/dhclient-8f9a3dff-24e6-4374-b0b2-c38524cdc0ce-eth0.lease Maybe there is some problem shutting down NetworkManager? I found the respective dhclient entries on two separate shutdown logs. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Fri Aug 2 19:30:06 2013 InstallationDate: Installed on 2013-04-10 (114 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) MarkForUpload: True ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=/dev/mapper/internal--ssd-root ro quiet SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Keine Berechtigung: '/etc/at.deny'] + --- + ApportVersion: 2.9.2-0ubuntu8.3 + Architecture: amd64 + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + CheckboxSubmission: b37fefbc97df4ba6a5f7edd504648fe4 + CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 + DistroRelease: Ubuntu 13.04 + IfupdownConfig: + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback + InstallationDate: Installed on 2013-04-10 (116 days ago) + InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130410) + IpRoute: + default via 192.168.178.1 dev eth0 proto static + 169.254.0.0/16 dev eth0 scope link metric 1000 + 192.168.178.0/24 dev eth0 proto kernel scope link src 192.168.178.21 metric 1 + IwConfig: + eth0 no wireless extensions. + + lono wireless extensions. + MarkForUpload: True + NetworkManager.state: + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true + NonfreeKernelModules: nvidia + Package: network-manager 0.9.8.0-0ubuntu6 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 + RfKill: + + Tags: raring + Uname: Linux 3.8.0-28-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark + mtime.conffile..etc.NetworkManager.dispatcher.d.01ifupdown: 2012-04-12T20:53:51 + nmcli-con: + NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH + Auto-Ethernet 8f9a3dff-24e6-4374-b0b2-c38524cdc0ce 802-3-ethernet1375699766 Mo 05 Aug 2013 12:49:26 CEST yes no /org/freedesktop/NetworkManager/Settings/2 + Xag56Rs#xP38d171a1-ae74-449a-ab52-39274a4dfb60 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/1 + HS-Fulda-VPN 44ed749b-56b2-42eb-8717-08e5e0ef49a6 vpn 1375200591 Di 30 Jul 2013 18:09:51 CEST yes no /org/freedesktop/NetworkManager/Settings/0 + nmcli-dev: + DEVICE TYPE STATE DBUS-PATH + eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 + nmcli-nm: + RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI W
Re: [Desktop-packages] [Bug 1084960] Re: [GeForce GT 430] Resume from Standby mode doesn't work with Nouveau
@madbiologist Thanks for the hint, but for me (on Geforce GT 430) resuming from suspend still doesn't work, even with kernel 3.10.rc-4 on Saucy. Am 08.06.2013 12:33, schrieb madbiologist: > For chips from the NVC0 family (GeForce/GT/GTS/GTX 4xx/5xx) this should > be fixed upstream in kernel 3.10 by commit > 6d5f83834dc2b064b8c1202ea281820286b675a8 and in the stable kernel 3.9.5 > by this commit: > > commit 44f781d513619ed4b6e6a1545d912b2733f65cce > Author: Ben Skeggs > Date: Mon May 13 16:11:12 2013 +1000 > > drm/nvc0/ce: disable ce1 on a number of chipsets > > commit 6d5f83834dc2b064b8c1202ea281820286b675a8 upstream. > > The falcon is present, but the rest of the copy engine doesn't appear to > be... PUNITS doesn't report disabled (maybe the bits for the copy > engines > got added later?), so we end up trying to use a non-functional CE1, and > bust all sorts of things.. Most notably, suspend/resume.. > > Signed-off-by: Ben Skeggs > Signed-off-by: Lingzhu Xiang > Signed-off-by: Greg Kroah-Hartman > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1084960 Title: [GeForce GT 430] Resume from Standby mode doesn't work with Nouveau Status in “linux” package in Ubuntu: Confirmed Status in “xserver-xorg-video-nouveau” package in Ubuntu: Triaged Bug description: Hello, if I'm using the Nouveau driver with my graphics board (Geforce GT430), standby mode (a.k.a. suspend-to-ram) does not work. Going into standby mode itself works, but when I turn my PC back on, the monitor shows just a kind of colorful "noise" with the usual mouse cursor (the cursor itself is displayed properly). Sometimes it's possible to move the cursor a bit, but the system can't be used anymore and has to rebooted with the Alt+Print+b keycombo. This also happens on Quantal when I use the Nouveau driver. With the propritary Nvidia driver, standby mode works fine. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6 Uname: Linux 3.7.0-3-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Nov 30 10:34:21 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2012-11-26 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-3-generic root=/dev/mapper/internal--hdd-test1 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.40-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.14-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Fri Nov 30 10:33:12 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Laser Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to
[Desktop-packages] [Bug 1168708] [NEW] Noveau driver isn't loaded anymore since kernel 3.2.0-39
Public bug reported: Hello, on this machine, since the newest kernel updates the Nouveau driver doesn't get loaded anymore (the graphic card is a Geforce 2 MX). The unfortunate consequence is that the screen resolution is limited to 1024x768. The last kernel version where the Nouveau driver works is 3.2.0-38 . If I run 3.2.0-39, 3.2.0-40 or the Quantal kernel 3.5.x, the Nouveau kernel modules are obviously not loaded during boot (the output of 'lsmod | grep nouveau' is empty). If I inspect the log files like /var/log/kern.log or /var/log/dmesg, I can't find any reference to the Nouveau driver and no possible hints why it wasn't loaded. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic-pae 3.2.40 Uname: Linux 3.2.0-40-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Apr 13 19:17:05 2013 DistUpgraded: 2012-09-09 13:25:23,873 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: NVIDIA Corporation NV11 [GeForce2 MX/MX 400] [10de:0110] (rev b2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. AGP-V7100 Pro [1043:4015] MarkForUpload: True PlymouthDebug: Error: [Errno 13] Keine Berechtigung: '/var/log/plymouth-debug.log' ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-40-generic-pae root=UUID=21f9d629-6568-4a6b-9b16-6b51bcaa1693 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to precise on 2012-09-09 (216 days ago) dmi.modalias: dmi: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.39-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.12 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1168708 Title: Noveau driver isn't loaded anymore since kernel 3.2.0-39 Status in “xserver-xorg-video-nouveau” package in Ubuntu: New Bug description: Hello, on this machine, since the newest kernel updates the Nouveau driver doesn't get loaded anymore (the graphic card is a Geforce 2 MX). The unfortunate consequence is that the screen resolution is limited to 1024x768. The last kernel version where the Nouveau driver works is 3.2.0-38 . If I run 3.2.0-39, 3.2.0-40 or the Quantal kernel 3.5.x, the Nouveau kernel modules are obviously not loaded during boot (the output of 'lsmod | grep nouveau' is empty). If I inspect the log files like /var/log/kern.log or /var/log/dmesg, I can't find any reference to the Nouveau driver and no possible hints why it wasn't loaded. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build3 ProcVersionSignature: Ubuntu 3.2.0-40.64-generic-pae 3.2.40 Uname: Linux 3.2.0-40-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Apr 13 19:17:05 2013 DistUpgraded: 2012-09-09 13:25:23,873 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: NVIDIA Corporation NV11 [GeForce2 MX/MX 400] [10de:0110] (rev b2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. AGP-V7100 Pro [1043:4015] MarkForUpload: True PlymouthDebug: Error: [Errno 13] Keine Berechtigung: '/var/log/plymouth-debug.log' ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-40-generic-pae root=UUID=21f9d629-6568-4a6b-9b16-6b51bcaa1693 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to precise on 2012-09-09 (216 days ago) dmi.modalias: dmi: versio
[Desktop-packages] [Bug 508065] Re: Changing 'Icon View Default' - 'Default zoom level' works once and not after
Nemo developers have already made the same change as in the patch: https://github.com/linuxmint/nemo/commit/60635d187d9c7ed48e2e6e6f2612ffc18cfe567c -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/508065 Title: Changing 'Icon View Default' - 'Default zoom level' works once and not after Status in Nautilus: Expired Status in “nautilus” package in Ubuntu: Triaged Status in “nautilus” package in Debian: New Bug description: Binary package hint: nautilus Under nautilus: 1. Click on 'Edit' 2. Click on preferences 3. Under the 'Views tab' 4. Change 'Default zoom level' in 'Icon View Defaults' from 100% to 66% What you will see: The icons will decrees in size. Now: 1. Change 'Default zoom level' in 'Icon View Defaults' from 66% to 100% What will happen: Nothing What should change to the correct size when a new size is selected. Note: The correct behaviour was present under the previous LTS. ProblemType: Bug Architecture: i386 Date: Fri Jan 15 18:47:48 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113) Package: nautilus 1:2.29.1-0ubuntu2 ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-10.14-generic SourcePackage: nautilus Tags: lucid Uname: Linux 2.6.32-10-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/508065/+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 508065] Re: Changing 'Icon View Default' - 'Default zoom level' works once and not after
I have also forwarded the patch to Debian (see corresponding remote bug watch). ** Bug watch added: Debian Bug tracker #681063 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681063 ** Also affects: nautilus (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681063 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/508065 Title: Changing 'Icon View Default' - 'Default zoom level' works once and not after Status in Nautilus: Expired Status in “nautilus” package in Ubuntu: Triaged Status in “nautilus” package in Debian: Unknown Bug description: Binary package hint: nautilus Under nautilus: 1. Click on 'Edit' 2. Click on preferences 3. Under the 'Views tab' 4. Change 'Default zoom level' in 'Icon View Defaults' from 100% to 66% What you will see: The icons will decrees in size. Now: 1. Change 'Default zoom level' in 'Icon View Defaults' from 66% to 100% What will happen: Nothing What should change to the correct size when a new size is selected. Note: The correct behaviour was present under the previous LTS. ProblemType: Bug Architecture: i386 Date: Fri Jan 15 18:47:48 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113) Package: nautilus 1:2.29.1-0ubuntu2 ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-10.14-generic SourcePackage: nautilus Tags: lucid Uname: Linux 2.6.32-10-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/508065/+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 508065] Re: Changing 'Icon View Default' - 'Default zoom level' works once and not after
I have also uploaded packages for Quantal and Precise to my PPA for easier testing: https://launchpad.net/~kaiserclaudius/+archive/ppa I just run a short test on Precise myself to confirm that the fix also works there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/508065 Title: Changing 'Icon View Default' - 'Default zoom level' works once and not after Status in Nautilus: Expired Status in “nautilus” package in Ubuntu: Triaged Bug description: Binary package hint: nautilus Under nautilus: 1. Click on 'Edit' 2. Click on preferences 3. Under the 'Views tab' 4. Change 'Default zoom level' in 'Icon View Defaults' from 100% to 66% What you will see: The icons will decrees in size. Now: 1. Change 'Default zoom level' in 'Icon View Defaults' from 66% to 100% What will happen: Nothing What should change to the correct size when a new size is selected. Note: The correct behaviour was present under the previous LTS. ProblemType: Bug Architecture: i386 Date: Fri Jan 15 18:47:48 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113) Package: nautilus 1:2.29.1-0ubuntu2 ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-10.14-generic SourcePackage: nautilus Tags: lucid Uname: Linux 2.6.32-10-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/508065/+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 508065] Re: Changing 'Icon View Default' - 'Default zoom level' works once and not after
I have added a patch that fixes the issue of the compact view default zoom level being ignored (while it actually wrongly reacted to the icon view default zoom level!), as described in the duplicates of this bug report. This patch is actually just a one line change which seems to be a typo in the original source code. I have tested it locally on my machine on Quantal, but it should also fix the bug for Nautilus in Precise since this is basically the same version of Nautilus. Unfortunately Nautilus upstream maintainers have dropped compact view since version 3.6, so I doubt that the patch will have any use for them. But I'll try to forward the patch to Nemo upstream. Kind regards, Jan ** Patch added: "22_fix-for-default-compact-zoomlevel.patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/508065/+attachment/3487196/+files/22_fix-for-default-compact-zoomlevel.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/508065 Title: Changing 'Icon View Default' - 'Default zoom level' works once and not after Status in Nautilus: Expired Status in “nautilus” package in Ubuntu: Triaged Bug description: Binary package hint: nautilus Under nautilus: 1. Click on 'Edit' 2. Click on preferences 3. Under the 'Views tab' 4. Change 'Default zoom level' in 'Icon View Defaults' from 100% to 66% What you will see: The icons will decrees in size. Now: 1. Change 'Default zoom level' in 'Icon View Defaults' from 66% to 100% What will happen: Nothing What should change to the correct size when a new size is selected. Note: The correct behaviour was present under the previous LTS. ProblemType: Bug Architecture: i386 Date: Fri Jan 15 18:47:48 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100113) Package: nautilus 1:2.29.1-0ubuntu2 ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-10.14-generic SourcePackage: nautilus Tags: lucid Uname: Linux 2.6.32-10-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/508065/+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 1010794] Re: Graphics/text corruptions in some applications with nouveau drivers
I have run a short test with Precise on a seperate partition (since I'm using Quantal now for daily purpose) and I didn't find any problems so far. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1010794 Title: Graphics/text corruptions in some applications with nouveau drivers Status in Accelerated Xorg driver for nVidia cards: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xserver-xorg-video-nouveau” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Fix Committed Status in “xserver-xorg-video-nouveau” source package in Precise: Invalid Status in “xorg-server” source package in Quantal: Fix Released Status in “xserver-xorg-video-nouveau” source package in Quantal: Invalid Status in “xorg-server” source package in Raring: Fix Released Status in “xserver-xorg-video-nouveau” source package in Raring: Fix Released Bug description: For xserver-xorg-video-nouveau sru: [IMPACT] * Enables SolidFill on fermi and kepler cards, increasing performance slightly. [TESTCASE] * start ubuntu software center * hover over some urls and icons, likely corruption already occurs at this point, the more you mover over the more it shows. * This wil not fix it completely, only make it occur less, see xorg-server below for the real fix. [Regression Potential] * This should be a safe fix, since it simply enables some code which was already created specifically for these cards, and with some testing it appears to work just fine. * I expect no regressions, but in the worst case this would result in garbage being sent to the card, which may cause it to do an unexplained hang or (more likely) errors in dmesg and worse glitches since nothing is being shown any more. [Other Info] * Doing solid fill in hardware is a pretty nice speedup for those who use valgrind to test code, and also seems to increase responsitivity a little on nouveau without valgrind, since it safes 2 memcpy's on host, 2 memcpy's on gpu, and a memset. For the xorg-server sru: [IMPACT] * Fallback to exa with gradients and solid pictures results in visual corruption, because sometimes the source or mark pixmaps from previous operations are used. This results in visual corruption when those fallbacks are triggered. The xxv-nouveau fix helps slightly because it disables fallback for solid fills, but gradients are still not handled so it still triggers it. [TESTCASE] * Start ubuntu software center on a geforce card that has exa acceleration enabled. * Highlight mouse over items * Notice display corruption. [Regression Potential] * The patch has been reviewed by upstream, but is not yet included (upstream can be slow). The most likely regression would be that suddenly other operations start failing to draw correctly, or worst case cause crashes but I do not think it is likely. [Other Info] See also http://www.mail-archive.com/xorg-devel@lists.x.org/msg33376.html [Original bug report] Hello, there are several serious graphic and text corruptions on Quantal with nouveau drivers (which are used by default). To reproduce: - Boot a Quantal live system or a fresh installation - Start software-center. - Move the mouse in its window or click anything. Result: Text and some graphics become massively corrupted (See also attached screenshots and short demo video). I have seen this kind of corruption so far in software-center, ubiquity-slideshow (during installation) and one time on filename text field of gtk-filechooser. Booting the system with "nomodeset" seems to make the problem go away, as well as installing the propritary Nvidia drivers. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.1.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 14.977209] [drm] nouveau :01:00.0: PMFB0_SUBP0: 0x037f0040 [ 14.977214] [drm] nouveau :01:00.0: PMFB0_SUBP1: 0x037f [ 22.821303] [drm] nouveau :01:00.0: PFIFO: unknown status 0x4000 [ 22.920011] eth0: no IPv6 routers present Date: Sat Jun 9 09:21:19 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2)
[Desktop-packages] [Bug 919801] Re: Unity dash file search is extremely slow
** Changed in: unity-lens-files (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-lens-files in Ubuntu. Matching subscriptions: dp-unity-lens-files https://bugs.launchpad.net/bugs/919801 Title: Unity dash file search is extremely slow Status in Unity Files Lens: Incomplete Status in Zeitgeist Framework: Incomplete Status in “unity-lens-files” package in Ubuntu: Confirmed Bug description: When I try to use the Unity dash search feature to navigate to files and folders, it is extremely slow. For example, if I hit the super button to launch the search and then type "Pictures" to get my pictures directory, it takes almost 5 seconds for the folder icon to show. In comparison, if I use Gnome-Do to navigate to my Pictures folder, it's basically instant. I have attached a video screencast so that you can see the problem for yourself. --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,vpswitch,place,session,imgpng,mousepoll,resize,gnomecompat,regex,snap,grid,wall,unitymtgrabhandles,animation,expo,ezoom,workarounds,fade,scale,unityshell] DistroRelease: Ubuntu 11.10 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413) NonfreeKernelModules: nvidia Package: unity 5.0.0~+bzr1825ubuntu0+611 PackageArchitecture: i386 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric running-unity Uname: Linux 3.0.0-14-generic i686 UnreportableReason: This is not a genuine Ubuntu package UpgradeStatus: Upgraded to oneiric on 2011-10-14 (99 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-files/+bug/919801/+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 1084960] Re: Resume from Standby mode doesn't work with Nouveau on Geforce GT430
I have added the kernel-bug-exists-upstream tag, since testing with Fedora 18 showed the same behaviour, so this seems to be an upstream bug. ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1084960 Title: Resume from Standby mode doesn't work with Nouveau on Geforce GT430 Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Hello, if I'm using the Nouveau driver with my graphics board (Geforce GT430), standby mode (a.k.a. suspend-to-ram) does not work. Going into standby mode itself works, but when I turn my PC back on, the monitor shows just a kind of colorful "noise" with the usual mouse cursor (the cursor itself is displayed properly). Sometimes it's possible to move the cursor a bit, but the system can't be used anymore and has to rebooted with the Alt+Print+b keycombo. This also happens on Quantal when I use the Nouveau driver. With the propritary Nvidia driver, standby mode works fine. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6 Uname: Linux 3.7.0-3-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Nov 30 10:34:21 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2012-11-26 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-3-generic root=/dev/mapper/internal--hdd-test1 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.40-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.14-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Fri Nov 30 10:33:12 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Laser Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.0-0ubuntu8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1084960/+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 1084960] Re: Resume from Standby mode doesn't work with Nouveau on Geforce GT430
I have tested the latest upstream kernel 3.8-rc1, the bug is also present there. However I'm not completely shure whether this is bug in the kernel or in the xorg-driver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1084960 Title: Resume from Standby mode doesn't work with Nouveau on Geforce GT430 Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Hello, if I'm using the Nouveau driver with my graphics board (Geforce GT430), standby mode (a.k.a. suspend-to-ram) does not work. Going into standby mode itself works, but when I turn my PC back on, the monitor shows just a kind of colorful "noise" with the usual mouse cursor (the cursor itself is displayed properly). Sometimes it's possible to move the cursor a bit, but the system can't be used anymore and has to rebooted with the Alt+Print+b keycombo. This also happens on Quantal when I use the Nouveau driver. With the propritary Nvidia driver, standby mode works fine. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6 Uname: Linux 3.7.0-3-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Nov 30 10:34:21 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2012-11-26 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-3-generic root=/dev/mapper/internal--hdd-test1 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.40-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.14-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Fri Nov 30 10:33:12 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Laser Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.0-0ubuntu8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1084960/+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 1084960] [NEW] Resume from Standby mode doesn't work with Nouveau on Geforce GT430
Public bug reported: Hello, if I'm using the Nouveau driver with my graphics board (Geforce GT430), standby mode (a.k.a. suspend-to-ram) does not work. Going into standby mode itself works, but when I turn my PC back on, the monitor shows just a kind of colorful "noise" with the usual mouse cursor (the cursor itself is displayed properly). Sometimes it's possible to move the cursor a bit, but the system can't be used anymore and has to rebooted with the Alt+Print+b keycombo. This also happens on Quantal when I use the Nouveau driver. With the propritary Nvidia driver, standby mode works fine. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6 Uname: Linux 3.7.0-3-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Nov 30 10:34:21 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2012-11-26 (4 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-3-generic root=/dev/mapper/internal--hdd-test1 ro quiet splash SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.40-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.14-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Fri Nov 30 10:33:12 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Laser Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.0-0ubuntu8 xserver.video_driver: nouveau ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring running-unity ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1084960 Title: Resume from Standby mode doesn't work with Nouveau on Geforce GT430 Status in “xserver-xorg-video-nouveau” package in Ubuntu: New Bug description: Hello, if I'm using the Nouveau driver with my graphics board (Geforce GT430), standby mode (a.k.a. suspend-to-ram) does not work. Going into standby mode itself works, but when I turn my PC back on, the monitor shows just a kind of colorful "noise" with the usual mouse cursor (the cursor itself is displayed properly). Sometimes it's possible to move the cursor a bit, but the system can't be used anymore and has to rebooted with the Alt+Print+b keycombo. This also happens on Quantal when I use the Nouveau driver. With the propritary Nvidia driver, standby mode works fine. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-3.9-generic 3.7.0-rc6 Uname: Linux 3.7.0-3-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CompizPlugins
[Desktop-packages] [Bug 1010794] Re: Graphics/text corruptions in some applications with nouveau drivers
I can also confirm that the updated package fixes this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1010794 Title: Graphics/text corruptions in some applications with nouveau drivers Status in Accelerated Xorg driver for nVidia cards: Fix Released Status in “xorg-server” package in Ubuntu: Fix Released Status in “xserver-xorg-video-nouveau” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Confirmed Status in “xserver-xorg-video-nouveau” source package in Precise: Triaged Status in “xorg-server” source package in Quantal: Fix Committed Status in “xserver-xorg-video-nouveau” source package in Quantal: Triaged Status in “xorg-server” source package in Raring: Fix Released Status in “xserver-xorg-video-nouveau” source package in Raring: Fix Released Bug description: For xserver-xorg-video-nouveau sru: [IMPACT] * Enables SolidFill on fermi and kepler cards, increasing performance slightly. [TESTCASE] * start ubuntu software center * hover over some urls and icons, likely corruption already occurs at this point, the more you mover over the more it shows. * This wil not fix it completely, only make it occur less, see xorg-server below for the real fix. [Regression Potential] * This should be a safe fix, since it simply enables some code which was already created specifically for these cards, and with some testing it appears to work just fine. * I expect no regressions, but in the worst case this would result in garbage being sent to the card, which may cause it to do an unexplained hang or (more likely) errors in dmesg and worse glitches since nothing is being shown any more. [Other Info] * Doing solid fill in hardware is a pretty nice speedup for those who use valgrind to test code, and also seems to increase responsitivity a little on nouveau without valgrind, since it safes 2 memcpy's on host, 2 memcpy's on gpu, and a memset. For the xorg-server sru: [IMPACT] * Fallback to exa with gradients and solid pictures results in visual corruption, because sometimes the source or mark pixmaps from previous operations are used. This results in visual corruption when those fallbacks are triggered. The xxv-nouveau fix helps slightly because it disables fallback for solid fills, but gradients are still not handled so it still triggers it. [TESTCASE] * Start ubuntu software center on a geforce card that has exa acceleration enabled. * Highlight mouse over items * Notice display corruption. [Regression Potential] * The patch has been reviewed by upstream, but is not yet included (upstream can be slow). The most likely regression would be that suddenly other operations start failing to draw correctly, or worst case cause crashes but I do not think it is likely. [Other Info] See also http://www.mail-archive.com/xorg-devel@lists.x.org/msg33376.html [Original bug report] Hello, there are several serious graphic and text corruptions on Quantal with nouveau drivers (which are used by default). To reproduce: - Boot a Quantal live system or a fresh installation - Start software-center. - Move the mouse in its window or click anything. Result: Text and some graphics become massively corrupted (See also attached screenshots and short demo video). I have seen this kind of corruption so far in software-center, ubiquity-slideshow (during installation) and one time on filename text field of gtk-filechooser. Booting the system with "nomodeset" seems to make the problem go away, as well as installing the propritary Nvidia drivers. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.1.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 14.977209] [drm] nouveau :01:00.0: PMFB0_SUBP0: 0x037f0040 [ 14.977214] [drm] nouveau :01:00.0: PMFB0_SUBP1: 0x037f [ 22.821303] [drm] nouveau :01:00.0: PFIFO: unknown status 0x4000 [ 22.920011] eth0: no IPv6 routers present Date: Sat Jun 9 09:21:19 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcEnviron: TERM=xterm PATH
[Desktop-packages] [Bug 1010794] Re: Graphics/text corruptions in some applications with nouveau drivers
Maarten, yes, your patches helped, I don't see these corruptions anymore with the patched package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1010794 Title: Graphics/text corruptions in some applications with nouveau drivers Status in “xserver-xorg-video-nouveau” package in Ubuntu: In Progress Bug description: Hello, there are several serious graphic and text corruptions on Quantal with nouveau drivers (which are used by default). To reproduce: - Boot a Quantal live system or a fresh installation - Start software-center. - Move the mouse in its window or click anything. Result: Text and some graphics become massively corrupted (See also attached screenshots and short demo video). I have seen this kind of corruption so far in software-center, ubiquity-slideshow (during installation) and one time on filename text field of gtk-filechooser. Booting the system with "nomodeset" seems to make the problem go away, as well as installing the propritary Nvidia drivers. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.1.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 14.977209] [drm] nouveau :01:00.0: PMFB0_SUBP0: 0x037f0040 [ 14.977214] [drm] nouveau :01:00.0: PMFB0_SUBP1: 0x037f [ 22.821303] [drm] nouveau :01:00.0: PFIFO: unknown status 0x4000 [ 22.920011] eth0: no IPv6 routers present Date: Sat Jun 9 09:21:19 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/dm-5 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1010794/+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 1064962] Re: Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running
I noticed that when I open a document and the LO window has no menu bar, the menu bar comes back when I'm minimizing the LO window and restoring it (e.g. clicking on its launcher icon). -- 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/1064962 Title: Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running Status in BAMF Application Matching Framework: Confirmed Status in The Application Menu: Confirmed Status in “bamf” package in Ubuntu: Confirmed Status in “indicator-appmenu” package in Ubuntu: Confirmed Status in “libreoffice” package in Ubuntu: Invalid Status in “bamf” source package in Quantal: Confirmed Status in “indicator-appmenu” source package in Quantal: Confirmed Status in “libreoffice” source package in Quantal: Invalid Bug description: 1) Have no instance of LibreOffice running 2) open a document by double-clicking it in nautilus 3) new window has no menu 4) unfocusing/refocusing (e.g. by pressing F7 to bring up the spelling dialog) makes the menu appear ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-gtk 1:3.6.2~rc2-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu2 Architecture: amd64 Date: Wed Oct 10 11:48:20 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to quantal on 2012-09-30 (9 days ago) original description: In writer, none of the menubar items appear to work. Example: * Open new document in Writer * Type some text and highlight it * Try Edit->Cut >> Nothing happens * Try Format->Change chase->UPPERCASE >> Nothing happens! workaround: restart your session after update To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1064962/+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 1010794] Re: Graphics/text corruptions in some applications with nouveau drivers
Still present at current stage. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1010794 Title: Graphics/text corruptions in some applications with nouveau drivers Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Hello, there are several serious graphic and text corruptions on Quantal with nouveau drivers (which are used by default). To reproduce: - Boot a Quantal live system or a fresh installation - Start software-center. - Move the mouse in its window or click anything. Result: Text and some graphics become massively corrupted (See also attached screenshots and short demo video). I have seen this kind of corruption so far in software-center, ubiquity-slideshow (during installation) and one time on filename text field of gtk-filechooser. Booting the system with "nomodeset" seems to make the problem go away, as well as installing the propritary Nvidia drivers. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.1.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 14.977209] [drm] nouveau :01:00.0: PMFB0_SUBP0: 0x037f0040 [ 14.977214] [drm] nouveau :01:00.0: PMFB0_SUBP1: 0x037f [ 22.821303] [drm] nouveau :01:00.0: PFIFO: unknown status 0x4000 [ 22.920011] eth0: no IPv6 routers present Date: Sat Jun 9 09:21:19 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/dm-5 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1010794/+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 1040495] Re: Graphical corruptions with Nouveau driver makes Quantal unusable
I did some further testing after installing the current daily image (only possible by booting the usb stick with "nomodeset"). It seems to depend on the boot options if the system comes up properly with Nouveau drivers (and KMS). Booting with just: quiet splash splash or no options specified as kernel options makes the system come up properly (even with 3D acceleration, allthough with bug #1010794). Otherwise, if I boot with: ro quiet splash $vt_handoff quiet splash $vt_handoff ro quiet splash it leads to the unusable desktop/login manager as reported in this bug's description. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1040495 Title: Graphical corruptions with Nouveau driver makes Quantal unusable Status in “xserver-xorg-video-nouveau” package in Ubuntu: New Bug description: Hello, since a few weeks I effectively can't run Quantal anymore due to strong graphical corruption when using the Nouveau driver (I have a Geforce GT430 card). To reproduce, I just have to boot a daily live image from a USB stick. The followings happens (as shown in the camera screenshots I'm gonna attach): - The boot logo (shown by Plymouth) is distorted - Then for some seconds a very weird looking corrupted screen appears - Then the desktop has loaded, but shows only corruptions instead of the wallpaper - The dock on the left screen side is shown correctly, but it's not possible to start/use any application - The mouse cursor isn't shown, due to "shades" of tooltips you can sometimes guess where the cursor might be This is a regression from Precise and early Quantal, where Nouveau drivers worked much better. To report this bug, I had to boot the daily live image with the "nomodeset" option. Even the new software-rendered Unity desktop you get in this case is barely usable due to heavy repainting issues, but that might be another bug. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CasperVersion: 1.321 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Thu Aug 23 08:24:12 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, even including gdb or git bisection work if needed GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120822) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- nomodeset debian-installer/language=de keyboard-configuration/layoutcode?=de SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8+bzr3249-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.904-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1040495/+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 1010794] Re: Graphics/text corruptions in some applications with nouveau drivers
Still present on current quantal daily image. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1010794 Title: Graphics/text corruptions in some applications with nouveau drivers Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Hello, there are several serious graphic and text corruptions on Quantal with nouveau drivers (which are used by default). To reproduce: - Boot a Quantal live system or a fresh installation - Start software-center. - Move the mouse in its window or click anything. Result: Text and some graphics become massively corrupted (See also attached screenshots and short demo video). I have seen this kind of corruption so far in software-center, ubiquity-slideshow (during installation) and one time on filename text field of gtk-filechooser. Booting the system with "nomodeset" seems to make the problem go away, as well as installing the propritary Nvidia drivers. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 ProcVersionSignature: Ubuntu 3.4.0-5.11-generic 3.4.0 Uname: Linux 3.4.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.1.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 14.977209] [drm] nouveau :01:00.0: PMFB0_SUBP0: 0x037f0040 [ 14.977214] [drm] nouveau :01:00.0: PMFB0_SUBP1: 0x037f [ 22.821303] [drm] nouveau :01:00.0: PFIFO: unknown status 0x4000 [ 22.920011] eth0: no IPv6 routers present Date: Sat Jun 9 09:21:19 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120606.2) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/dm-5 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F13 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd07/10/2008:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.7.8-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.19.0-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20120322+ab7291d-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1010794/+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
