[Touch-packages] [Bug 1523029] [NEW] Install on Lenovo S21e: Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error
Public bug reported: Trying to install Ubuntu 14.04 LTS on a Lenovo S21e. When running the installer, I get the following error message: "Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error" I've tried pressing "Retry" several times. Message was persistent. When selecting to choose the whole drive, the partitions are not created automatically. Any help/hints greatly appreciated. Thanks in advance :) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1523029 Title: Install on Lenovo S21e: Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error Status in systemd package in Ubuntu: New Bug description: Trying to install Ubuntu 14.04 LTS on a Lenovo S21e. When running the installer, I get the following error message: "Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error" I've tried pressing "Retry" several times. Message was persistent. When selecting to choose the whole drive, the partitions are not created automatically. Any help/hints greatly appreciated. Thanks in advance :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1523029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1523029] Re: Install on Lenovo S21e: Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error
Maybe it's related, but when I choose to use the whole drive, auto-partitioning fails. The installer just shows the existing Windows8 partitions. Pressing "Install Now" replies that a partition to install to must be chosen first. I remember that there was auto-partitioning in that step. No manual interaction with partitioning needed. I've now tried the "install alongside Windows" option. That one seems to work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1523029 Title: Install on Lenovo S21e: Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error Status in systemd package in Ubuntu: New Bug description: Trying to install Ubuntu 14.04 LTS on a Lenovo S21e. When running the installer, I get the following error message: "Error fsyncing/closing /dev/mmcblk0rpmb: Input/output error" I've tried pressing "Retry" several times. Message was persistent. When selecting to choose the whole drive, the partitions are not created automatically. Any help/hints greatly appreciated. Thanks in advance :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1523029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1523041] [NEW] Lenovo S21e: brightness keys seem inversed
Public bug reported: Fresh install of Xubuntu Trusty (14.04.3 64bit) on a Lenovo S21e. The brightness +/- keys work, but their function seems to be reversed: - minus makes it brighter - plus makes it darker Additionally, the screen goes completely off (no backlight) when reaching the lowest or highest brightness step. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1523041 Title: Lenovo S21e: brightness keys seem inversed Status in systemd package in Ubuntu: New Bug description: Fresh install of Xubuntu Trusty (14.04.3 64bit) on a Lenovo S21e. The brightness +/- keys work, but their function seems to be reversed: - minus makes it brighter - plus makes it darker Additionally, the screen goes completely off (no backlight) when reaching the lowest or highest brightness step. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1523041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1523041] Re: Lenovo S21e: brightness keys seem inversed
The issue seems to be fixed in 14.04.4 (64bit). Just installed it fresh on another Lenovo S21e-20 (same model as previously), and brightness control now works as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1523041 Title: Lenovo S21e: brightness keys seem inversed Status in systemd package in Ubuntu: Incomplete Bug description: Fresh install of Xubuntu Trusty (14.04.3 64bit) on a Lenovo S21e. The brightness +/- keys work, but their function seems to be reversed: - minus makes it brighter - plus makes it darker Additionally, the screen goes completely off (no backlight) when reaching the lowest or highest brightness step. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1523041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1523041] Re: Lenovo S21e: brightness keys seem inversed
** Changed in: systemd (Ubuntu) Status: Expired => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1523041 Title: Lenovo S21e: brightness keys seem inversed Status in systemd package in Ubuntu: Fix Released Bug description: Fresh install of Xubuntu Trusty (14.04.3 64bit) on a Lenovo S21e. The brightness +/- keys work, but their function seems to be reversed: - minus makes it brighter - plus makes it darker Additionally, the screen goes completely off (no backlight) when reaching the lowest or highest brightness step. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1523041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676092] Re: Can't install audacious in Xenial depends not the right version
I just ran into the exact same error message trying to install "gresolver": "libgail18 : Depends: libgtk2.0-0 (= 2.24.30-1ubuntu1) but 2.24.30-1ubuntu1.16.04.1 is to be installed" When I enable "xenial-updates main" the dependency error disappears and I can install the required libgtk packages. My distro is Xubuntu 16.04.3. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1676092 Title: Can't install audacious in Xenial depends not the right version Status in audacious package in Ubuntu: Confirmed Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: When trying to install Audacious I need to install it's dependancy gtk2-engines-pixbuf which can't be installed, because it needs "libgtk2.0-0 (= 2.24.30-1ubuntu1)" but " 2.24.30-1ubuntu1.16.04.1" is installed. (is it the same version with a different name? ) Therefore, no Audacious… :-/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1676092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1740939] [NEW] Endless "cycling" of menu item selection
Public bug reported: On a fresh install of Xubuntu 16.04, I've noticed the following issue: When I press a "special" key on the keyboard, like "XF86Homepage" while having a Qt-based application running and focused, I'm unable to use any (context-)menu of that application anymore: It's like one would keep pressing the "down" arrow key whenever I open a menu. Sometimes even random options get selected after a few seconds (unless I press "Esc" to exit the menu fast enough). First I thought it was an issue with "Clementine" music player, but just now, I've had the same issue with "vokoscreen". That's why I assume it's an issue with Qt :( Thank you very much in advance. ** Affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1740939 Title: Endless "cycling" of menu item selection Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: On a fresh install of Xubuntu 16.04, I've noticed the following issue: When I press a "special" key on the keyboard, like "XF86Homepage" while having a Qt-based application running and focused, I'm unable to use any (context-)menu of that application anymore: It's like one would keep pressing the "down" arrow key whenever I open a menu. Sometimes even random options get selected after a few seconds (unless I press "Esc" to exit the menu fast enough). First I thought it was an issue with "Clementine" music player, but just now, I've had the same issue with "vokoscreen". That's why I assume it's an issue with Qt :( Thank you very much in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1740939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1222356] Re: WARNING: Couldn't register with accessibility bus: Did not receive a reply.
I know this thread is ancient and marked as fixed, but I just ran into the exact same error message on a recently installed Xubuntu 18.04.4, opening Thunderbird (1:68.8.0+build2-0ubuntu0.18.04.2) after resuming from suspend: Quote from "~/.xsession-errors": ``` (nm-applet:26135): Gtk-WARNING **: 18:53:46.496: Can't set a parent on widget which has a parent (wrapper-1.0:26197): GLib-CRITICAL **: 18:53:57.168: Source ID 174 was not found when attempting to remove it Gtk-Message: 18:55:17.424: GtkDialog mapped without a transient parent. This is discouraged. (exo-open:329): dbind-WARNING **: 18:55:21.445: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (exo-helper-1:331): dbind-WARNING **: 18:55:21.459: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. JavaScript error: chrome://coloredfolders/content/coloredfolders.js, line 118: TypeError: elm is null ``` I haven't done anything fancy on this system that I'm aware of, so someone else might also get this warning message on a recent setup? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1222356 Title: WARNING: Couldn't register with accessibility bus: Did not receive a reply. Status in at-spi2-core package in Ubuntu: Fix Released Status in at-spi2-core package in Debian: Fix Released Bug description: The following warnings/errors appear after calling ubuntu-bug ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport-gtk 2.12.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 10:54:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-01 (371 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1222356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1947405] [NEW] pm-suspend does not lock screen
Public bug reported: System: Xubuntu 20.04.3 (64bit) When suspending my notebook by calling "/usr/sbin/pm-suspend", there is **no login dialog** after resuming. If I suspend using the graphical XFCE logout menu, the screen is locked properly. I've checked on my other 18.04 machine: There, pm-suspend locks the screen as expected. Is this something to be configured or a parameter? Grateful for any hints :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pm-utils 1.4.1-19 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 15 19:39:23 2021 InstallationDate: Installed on 2021-01-16 (271 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1947405 Title: pm-suspend does not lock screen Status in pm-utils package in Ubuntu: New Bug description: System: Xubuntu 20.04.3 (64bit) When suspending my notebook by calling "/usr/sbin/pm-suspend", there is **no login dialog** after resuming. If I suspend using the graphical XFCE logout menu, the screen is locked properly. I've checked on my other 18.04 machine: There, pm-suspend locks the screen as expected. Is this something to be configured or a parameter? Grateful for any hints :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pm-utils 1.4.1-19 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 15 19:39:23 2021 InstallationDate: Installed on 2021-01-16 (271 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1947405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1947405] Re: pm-suspend does not lock screen
Oh! On the 18.04 machine I actually executed: `xfce4-session-logout --suspend` Now realizing this, I'm asking myself if this issue should be closed since "pm-suspend" isn't supposed to lock, because that's "xflock4" job, right? :| Sorry for the noise. Yet, I hope it may at least point others towards "xfce4-session-logout" when suspending by command :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1947405 Title: pm-suspend does not lock screen Status in pm-utils package in Ubuntu: New Bug description: System: Xubuntu 20.04.3 (64bit) When suspending my notebook by calling "/usr/sbin/pm-suspend", there is **no login dialog** after resuming. If I suspend using the graphical XFCE logout menu, the screen is locked properly. I've checked on my other 18.04 machine: There, pm-suspend locks the screen as expected. Is this something to be configured or a parameter? Grateful for any hints :) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pm-utils 1.4.1-19 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 15 19:39:23 2021 InstallationDate: Installed on 2021-01-16 (271 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1947405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
