[Bug 1912950] [NEW] rsync halts with Permission denied (13) with a sticky dir and only recent kernels

2021-01-24 Thread Mathieu L BOUCHARD 
Public bug reported:

Looks like rsync should be adapted to a new policy of the Linux kernel.
I found a report in the ZFS Github that looks a lot like my problem :
https://github.com/openzfs/zfs/issues/10742 But on that page, the
suggested solution using /proc/sys/fs/protected_regular doesn't seem to
be ideal and instead rsync should be able to figure it out by itself so
that users aren't encouraged to keep that security measure turned off
(perhaps my idea is bad, but pros and cons have to be figured out).

I'm regularly backing up a remote folder on a machine that has a
different user list and that folder has sticky bit set, while being root
on both sides. I had no error using Ubuntu 18.04 : it started failing
just after upgrading to 20.04. If I try to rsync individual files of
that folder, I get error 13 in most cases, but if I chmod -t on that
folder, I can rsync them, but if I try rsyncing the folder again (by
recursion), rsync does chmod +t on it before rsyncing individual files
in the folder, and then it fails again. And of course, to work around
the problem, rsync would probably have to catch error 13 and retry after
doing chmod -t temporarily on the folder, then schedule a chmod +t after
this folder is finished syncing, or at cleanup time (Ctrl+c or SIGTERM).

** Affects: rsync (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Looks like rsync should be adapted to a new policy of the Linux kernel.
  I found a report in the ZFS Github that looks a lot like my problem :
  https://github.com/openzfs/zfs/issues/10742 But on that page, the
  suggested solution using /proc/sys/fs/protected_regular doesn't seem to
  be ideal and instead rsync should be able to figure it out by itself so
  that users aren't encouraged to keep that security measure turned off
  (perhaps my idea is bad, but pros and cons have to be figured out).
  
  I'm regularly backing up a remote folder on a machine that has a
  different user list and that folder has sticky bit set, while being root
  on both sides. I had no error using Ubuntu 18.04 : it started failing
  just after upgrading to 20.04. If I try to rsync individual files of
  that folder, I get error 13 in most cases, but if I chmod -t on that
- folder, I can rsync them, but after that, if I try rsyncing the folder
- again, rsync does chmod +t on it before rsyncing individual files in the
- folder, and then it fails again. And of course, to work around the
- problem, rsync would probably have to catch error 13 and retry after
+ folder, I can rsync them, but if I try rsyncing the folder again (by
+ recursion), rsync does chmod +t on it before rsyncing individual files
+ in the folder, and then it fails again. And of course, to work around
+ the problem, rsync would probably have to catch error 13 and retry after
  doing chmod -t temporarily on the folder, then schedule a chmod +t after
  this folder is finished syncing, or at cleanup time (Ctrl+c or SIGTERM).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912950

Title:
  rsync halts with Permission denied (13) with a sticky dir and only
  recent kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1912950/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1840055] Re: package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to install/upgrade: installed mariadb-server-10.1 package post-installation script subprocess returned error exit st

2019-10-20 Thread Mathieu L BOUCHARD 
Faustin, the problem happened when just doing a daily suggested software
update (some new updates show up, i click upgrade). AFAIK I am using
default settings for MariaDB and AppArmor (I don't think I've ever touched
AppArmor settings on any machine ever). A default install of MariaDB
shouldn't need any tricks just for a daily upgrade to run correctly. I
could try purging the package and reinstall it from scratch but I don't
know whether the problem will come back and I might have to install an
older version just to simulate...

Sorry, I never really finished this email. In the end I uninstalled mariadb
because I decided to use
something else for my project (for different reasons).


Le mar. 20 août 2019 à 15:50, Faustin <1840...@bugs.launchpad.net> a écrit :

> Hi Mathieu,
> thank you for your report and for your help making Ubuntu better.
>
> It is difficult to understand your problem because you do not provide
> the steps that would permit me to try to reproduce it.
>
> But I can see in the 'Dmesg.txt' log the following lines:
> [594512.788195] audit: type=1400 audit(1565709492.804:91):
> apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"
> name="/etc/ld.so.cache" pid=21185 comm="mysqld" requested_mask="r"
> denied_mask="r" fsuid=0 ouid=0
> [594512.788226] audit: type=1400 audit(1565709492.804:92):
> apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"
> name="/lib/x86_64-linux-gnu/libaio.so.1.0.1" pid=21185 comm="mysqld"
> requested_mask="r" denied_mask="r" fsuid=0 ouid=0
> [594512.793206] audit: type=1400 audit(1565709492.808:93):
> apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"
> name="/etc/ld.so.cache" pid=21190 comm="mysqld" requested_mask="r"
> denied_mask="r" fsuid=0 ouid=0
> [594512.793230] audit: type=1400 audit(1565709492.808:94):
> apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"
> name="/lib/x86_64-linux-gnu/libaio.so.1.0.1" pid=21190 comm="mysqld"
> requested_mask="r" denied_mask="r" fsuid=0 ouid=0
>
> This may be the reason of your problem.
>
> May I suggest you to try this (see my first comment):
>
> https://mariadb.com/kb/en/library/the-community-mariadb-troubles-only-running-after-reboot-times-out-when-try/
>
> Regards,
> Faustin
>
> ** Changed in: mariadb-10.1 (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1840055
>
> Title:
>   package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to
>   install/upgrade: installed mariadb-server-10.1 package post-
>   installation script subprocess returned error exit status 127
>
> Status in mariadb-10.1 package in Ubuntu:
>   Incomplete
>
> Bug description:
>   no idea, just an automated bug report that didn't tell me what the
>   actual problem is.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 18.04
>   Package: mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1
>   ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
>   Uname: Linux 4.15.0-55-generic x86_64
>   NonfreeKernelModules: mt76xx mt7630e
>   .etc.apparmor.d.usr.sbin.mysqld: /usr/sbin/mysqld { }
>   ApportVersion: 2.20.9-0ubuntu7.7
>   Architecture: amd64
>   Date: Tue Aug 13 11:18:12 2019
>   DuplicateSignature:
>package:mariadb-server-10.1:1:10.1.41-0ubuntu0.18.04.1
>Setting up mariadb-server-10.1 (1:10.1.41-0ubuntu0.18.04.1) ...
>dpkg: error processing package mariadb-server-10.1 (--configure):
> installed mariadb-server-10.1 package post-installation script
> subprocess returned error exit status 127
>   ErrorMessage: installed mariadb-server-10.1 package post-installation
> script subprocess returned error exit status 127
>   InstallationDate: Installed on 2016-02-08 (1282 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   Logs.var.log.daemon.log:
>
>   Logs.var.log.mysql.error.log:
>   MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
>   MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
>[mysqldump]
>quick
>quote-names
>max_allowed_packet   = 16M
>   MySQLVarLibDirListing: ['mysql_upgrade_info', 'ib_logfile0',
> 'ib_logfile1', 'multi-master.info', 'ibdata1', 'aria_log.0001',
> 'debian-10.1.flag', 'performance_schema', 'mysql', 'aria_log_control',
> 'bioapt']
>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
> root=UUID=6e93328c-e2f2-406c-843c-122c758dbb2a ro quiet splash vt.handoff=1
>   Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal,
> 3.6.7-1~18.04
>   PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal,
> 2.7.15~rc1-1
>   RelatedPackageVersions:
>dpkg 1.19.0.5ubuntu2.1
>apt  1.6.11
>   SourcePackage: mariadb-10.1
>   Title: package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to
> install/upgrade: installed mariadb-server-10.1 package post-installation
> script subprocess returned error exit status 127
>   UpgradeStatus: Upgraded to bionic on 2018-11-01 (285 days ago)

[Bug 1840055] Re: package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to install/upgrade: installed mariadb-server-10.1 package post-installation script subprocess returned error exit status

2019-08-14 Thread Mathieu L BOUCHARD 
A database server living exclusively in /var has no business touching
anything in /home, and has even less business umounting it. But I can't
confirm this from just running the dpkg command, as all it tells me is
"127" even when I run it with option "-D7". /var/log/apt/history.log
is even worse, as it doesn't even mention the "127" nor the subprocess
failing, just "dpkg" returning "1". I don't see any mention of "home" in
any file of /etc/mysql/ recursively. I'll try ProtectHome=false only
once I get a satisfying error message... but then, it's because I don't
rely on mariadb/mysql on this box.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840055

Title:
  package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to
  install/upgrade: installed mariadb-server-10.1 package post-
  installation script subprocess returned error exit status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1840055/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1840055] Re: package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to install/upgrade: installed mariadb-server-10.1 package post-installation script subprocess returned error exit st

2019-08-14 Thread Mathieu L BOUCHARD 
A database server living exclusively in /var has no business touching
anything in /home, and has even less business umounting it. But I can't
confirm this from just running the dpkg command, as all it tells me is
"127" even when I run it with option "-D7". /var/log/apt/history.log is
even worse, as it doesn't even mention the "127" nor the subprocess
failing, just "dpkg" returning "1". I don't see any mention of "home" in
any file of /etc/mysql/ recursively. I'll try ProtectHome=false only once I
get a satisfying error message... but then, it's because I don't rely on
mariadb/mysql on this box.


Le mer. 14 août 2019 à 12:00, Theo Nolte <1840...@bugs.launchpad.net> a
écrit :

> I had exactly the same problem. Changing "ProtectHome=true" to
> "ProtectHome=false" in the Unit-File fixed it for me. systemd was trying
> to unmount /home, which was not possible because of a lot of bind mounts
> on /home.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1840055
>
> Title:
>   package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to
>   install/upgrade: installed mariadb-server-10.1 package post-
>   installation script subprocess returned error exit status 127
>
> Status in mariadb-10.1 package in Ubuntu:
>   New
>
> Bug description:
>   no idea, just an automated bug report that didn't tell me what the
>   actual problem is.
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 18.04
>   Package: mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1
>   ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
>   Uname: Linux 4.15.0-55-generic x86_64
>   NonfreeKernelModules: mt76xx mt7630e
>   .etc.apparmor.d.usr.sbin.mysqld: /usr/sbin/mysqld { }
>   ApportVersion: 2.20.9-0ubuntu7.7
>   Architecture: amd64
>   Date: Tue Aug 13 11:18:12 2019
>   DuplicateSignature:
>package:mariadb-server-10.1:1:10.1.41-0ubuntu0.18.04.1
>Setting up mariadb-server-10.1 (1:10.1.41-0ubuntu0.18.04.1) ...
>dpkg: error processing package mariadb-server-10.1 (--configure):
> installed mariadb-server-10.1 package post-installation script
> subprocess returned error exit status 127
>   ErrorMessage: installed mariadb-server-10.1 package post-installation
> script subprocess returned error exit status 127
>   InstallationDate: Installed on 2016-02-08 (1282 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   Logs.var.log.daemon.log:
>
>   Logs.var.log.mysql.error.log:
>   MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
>   MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
>[mysqldump]
>quick
>quote-names
>max_allowed_packet   = 16M
>   MySQLVarLibDirListing: ['mysql_upgrade_info', 'ib_logfile0',
> 'ib_logfile1', 'multi-master.info', 'ibdata1', 'aria_log.0001',
> 'debian-10.1.flag', 'performance_schema', 'mysql', 'aria_log_control',
> 'bioapt']
>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
> root=UUID=6e93328c-e2f2-406c-843c-122c758dbb2a ro quiet splash vt.handoff=1
>   Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal,
> 3.6.7-1~18.04
>   PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal,
> 2.7.15~rc1-1
>   RelatedPackageVersions:
>dpkg 1.19.0.5ubuntu2.1
>apt  1.6.11
>   SourcePackage: mariadb-10.1
>   Title: package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to
> install/upgrade: installed mariadb-server-10.1 package post-installation
> script subprocess returned error exit status 127
>   UpgradeStatus: Upgraded to bionic on 2018-11-01 (285 days ago)
>   modified.conffile..etc.apparmor.d.usr.sbin.mysqld: [modified]
>   mtime.conffile..etc.apparmor.d.usr.sbin.mysqld:
> 2019-07-10T01:22:38.693495
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1840055/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840055

Title:
  package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to
  install/upgrade: installed mariadb-server-10.1 package post-
  installation script subprocess returned error exit status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1840055/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1840055] [NEW] package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to install/upgrade: installed mariadb-server-10.1 package post-installation script subprocess returned error exit stat

2019-08-13 Thread Mathieu L BOUCHARD 
Public bug reported:

no idea, just an automated bug report that didn't tell me what the
actual problem is.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
Uname: Linux 4.15.0-55-generic x86_64
NonfreeKernelModules: mt76xx mt7630e
.etc.apparmor.d.usr.sbin.mysqld: /usr/sbin/mysqld { }
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Tue Aug 13 11:18:12 2019
DuplicateSignature:
 package:mariadb-server-10.1:1:10.1.41-0ubuntu0.18.04.1
 Setting up mariadb-server-10.1 (1:10.1.41-0ubuntu0.18.04.1) ...
 dpkg: error processing package mariadb-server-10.1 (--configure):
  installed mariadb-server-10.1 package post-installation script subprocess 
returned error exit status 127
ErrorMessage: installed mariadb-server-10.1 package post-installation script 
subprocess returned error exit status 127
InstallationDate: Installed on 2016-02-08 (1282 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Logs.var.log.daemon.log:
 
Logs.var.log.mysql.error.log: 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLVarLibDirListing: ['mysql_upgrade_info', 'ib_logfile0', 'ib_logfile1', 
'multi-master.info', 'ibdata1', 'aria_log.0001', 'debian-10.1.flag', 
'performance_schema', 'mysql', 'aria_log_control', 'bioapt']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic 
root=UUID=6e93328c-e2f2-406c-843c-122c758dbb2a ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.11
SourcePackage: mariadb-10.1
Title: package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to 
install/upgrade: installed mariadb-server-10.1 package post-installation script 
subprocess returned error exit status 127
UpgradeStatus: Upgraded to bionic on 2018-11-01 (285 days ago)
modified.conffile..etc.apparmor.d.usr.sbin.mysqld: [modified]
mtime.conffile..etc.apparmor.d.usr.sbin.mysqld: 2019-07-10T01:22:38.693495

** Affects: mariadb-10.1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apparmor apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840055

Title:
  package mariadb-server-10.1 1:10.1.41-0ubuntu0.18.04.1 failed to
  install/upgrade: installed mariadb-server-10.1 package post-
  installation script subprocess returned error exit status 127

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1840055/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-04-22 Thread Mathieu L BOUCHARD 
Started experiencing this in Ubuntu 18.04 on two different computers,
since a few days ago, presumably because of a package upgrade ; both
users are using the Unity shell (if it makes any difference; I didn't
try another one) ; disabling those shortcuts is important because
Alt+arrow are very commonly used as Back/Forward in Chromium and
Firefox, whereas the virtual console feature is almost never used and
doesn't deserve more than just the usual Ctrl+Alt+Fn bindings. The
dumpkeys|grep|loadkeys hack works, but the problem is that it shouldn't
ever be needed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/520546

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772706] [NEW] USABILITY : "Add Bookmark"'s insertion into bookmark list moves all bookmarks downwards

2018-05-22 Thread Mathieu L BOUCHARD 
Public bug reported:

Drag-and-drop to a folder listed in bookmarks causes the list of
bookmarks to move down as the "Add Bookmark" item inserts itself above
the bookmark list when the dragging enters the bookmarks list. If
approached from the right side and expecting to be able to drop
immediately in a bookmarked folder, this will move the dragged thing to
the wrong folder (the one just above in the list) or will add it to the
list (if the target was the first bookmark). At best, it makes the user
be surprised and slowed down to adjust position, or it makes the user
getting used to having to aim 1 item lower in the list.

Possible improvements (not all equally good) :

(a) Make "Add Bookmark" appear as soon as an item goes into drag mode.

(b) Make "Add Bookmark" always present

(c) Add a "Bookmarks" heading to the bookmarks list and have a "+"
button next to it, that can either be dragged to, or pressed to open a
folder selection dialogue.

(d) Make "Add Bookmark" appear below the list (but if there is a
scrollbar for the left pane, what should happen to it ?)

(e) Make "Add Bookmark" appear outside the list (as a floating element
nearby, or inside the black toolbar at the top of the window).

(f) any other ideas ?


Note : I am using Ubuntu 16.04.4 and 17.10, with Unity. This is not a "bug" per 
se, but it's not a support question either, which is not I didn't file it on 
the Answers or AskUbuntu sites instead.

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: error-prone usability

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772706

Title:
  USABILITY : "Add Bookmark"'s insertion into bookmark list moves all
  bookmarks downwards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1772706/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1673072] Re: Open apps (even basic system ones) can still be missing from Alt+Tab

2017-03-15 Thread Mathieu L BOUCHARD 
By a strange coincidence, I just found a fourth bug, and I'm sure I've
never seen this before. I started /usr/bin/mplayer from commandline,
which opened a window (with default -vo setting), and it became listed
as a window of /usr/bin/firefox in both Alt+Tab and Dock. It didn't
happen again. You will probably not be able to reproduce it easily (I've
never seen this despite doing this over 1000 times since I first
installed Unity), but that's normal, that's the case of many race-
conditions, and this looks like one. There is often no other solution
than just reading source code to make sure it does no mistake about
locking or atomicity (whatever happens to be needed in that area of the
code).

In contrast, the second and third bugs (see description above) have
happened systematically for years. For the first bug, I don't know, it's
harder to notice.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673072

Title:
  Open apps (even basic system ones) can still be missing from Alt+Tab

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1673072/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1673072] Re: Open apps (even basic system ones) can still be missing from Alt+Tab

2017-03-15 Thread Mathieu L BOUCHARD 
I had actually chosen a more general title than that (something like «
Dock and Alt+tab can still have discrepancies about open apps (even
basic system ones) »).

However, I did so in the 2nd form while writing the description, and
Launchpad ignored it, and instead it took the original title I wrote in
the 1st form. And now I can't even edit it. This looks like a bug in
Launchpad (but I'm not in a position to confirm that bug without posting
a dummy bug report... please, someone, report it for me, if you can test
it).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673072

Title:
  Open apps (even basic system ones) can still be missing from Alt+Tab

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1673072/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1673072] [NEW] Open apps (even basic system ones) can still be missing from Alt+Tab

2017-03-15 Thread Mathieu L BOUCHARD 
Public bug reported:

After five years of Unity, it is still possible to have discrepancies
between those three lists :

1. apps that are really open

2. apps that are marked as open in the dock

3. apps that are switchable from Alt+Tab

First bug : I just noticed that the Software Update app appears in (1)
and (2) but not in (3). This also means that it's not possible to switch
between its windows using Alt+backtick.

I report this as a bug in Unity instead of Software Update because I
believe that this is a more general problem that affects several apps. I
don't know Unity's APIs, but if apps are asked to report themselves so
that they appear in the dock and Alt+tab, and if it's easy to get it
wrong, then various apps will get it wrong, possibly even system ones
(see also my other bug report, which is about menubars). But if ever it
doesn't work that way and it's already fully centralised, then it's a
bug in Unity anyway.

I distinguish the lists (1) and (2) because it's possible that they be
different, and it could be considered as two other bugs if you will.
Those problems happen more systematically instead of seeming like random
mistakes in various apps' source code.

Second bug : it's possible and easy for an app to add one question-mark
dock icon per window. This seems to be the default behaviour in Tcl/Tk,
as the PureData app does this for every "patcher window" (document
window) that is open (it doesn't happen with properties windows (though
they're nonmodal) because they are marked as belonging to a specific
document, so that Alt+tabbing to that document brings a group of windows
at once.

Third bug : an app can have an icon associated to it but have the dock
unable to figure out that the matching app has been launched. For
example, if I launch PureData (/usr/bin/pd) from the dock or the app
search, the "Pd" icon shows up blinking and looks like PureData is
taking a long time to launch or has crashed during launch, but meanwhile
(and very quickly) PureData's main window pops up and appears in the
dock as a question mark. If I open PureData from a Terminal instead, I
get no PureData icon and only the question mark icon. This whole problem
could have a toolkit-specific solution (set the icon from the app
instead of from a launch item) but it could also have a global solution
involving an ability to get the name of the executable of the X11
connection that opened the app (obviously, it wouldn't work with remote
X11 apps, but those are rare, so it would be ok). It would have to check
for child processes, though, as PureData's gui is a child process of
/usr/bin/pd.

I also stumbled upon that bug when making a launch item for a specific
Windows app. When clicking on that app in the dock, the dock added a
WINE icon to itself instead, and failed to recognise that the icon I had
clicked on was for an app that had completed launching (it kept
blinking, and the triangle did not appear there, because it appeared
next to the WINE icon instead).

** Affects: unity (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673072

Title:
  Open apps (even basic system ones) can still be missing from Alt+Tab

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1673072/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1321066] [NEW] xchat-gnome not visible in dock, unreachable when minimised

2014-05-19 Thread Mathieu L BOUCHARD 
Public bug reported:

Starting xchat-gnome does not put an icon in the dock. If I switch to a
different window, I can't reach it by Alt+tab : I have to minimise other
windows until I reach the xchat window. However, if I ever minimise the
xchat window itself, I can't ever reach it again, because it is not in
the dock, it is not in Alt+tab, AND it is not in the letter-shaped
indicator/applet, unlike what it looks like : when clicking on the
xchat item in that menu, it starts a new xchat, over and over.

This problem happened to me with several other apps since the beginning
of the gnome3/unity era (even OOCalc, a very important app). It never
ever happened in gnome2 days (or before) : it was essentially impossible
to lose an app window this way. Therefore I think that the best way to
fix this bug is most certainly in the gnome infrastructure itself,
though in the meantime, fixing this bug at the level of xchat-gnome
would make it less unusable (I would not attempt to use it in that
state).

The app named just xchat does appear in the dock and Alt+tab.

This is on a fresh install of 12.04 immediately upgraded to 14.04 before
trying the above (if it matters at all).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xchat-gnome 1:0.30.0~git20131003.d20b8d+really20110821-0.2ubuntu12
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: i386
CurrentDesktop: Unity
Date: Mon May 19 21:43:41 2014
InstallationDate: Installed on 2014-05-18 (1 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 
(20130820.1)
SourcePackage: xchat-gnome
UpgradeStatus: Upgraded to trusty on 2014-05-18 (1 days ago)

** Affects: xchat-gnome (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321066

Title:
  xchat-gnome not visible in dock, unreachable when minimised

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1321066/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1067450] [NEW] burning a cd + renaming a folder at the same time causes freeze then crash

2012-10-16 Thread Mathieu L BOUCHARD 
Public bug reported:

I used Nautilus to burn a CD image. This creates a «Transient» window
which is not modal, but trying to use the window underneath to do
something as simple as renaming a folder (F2 key) in the same folder
causes Nautilus to NOT do the rename, just wait, then the window goes
dark, then after some more seconds it just shutdowns without any
explanation (not even a dialogue box saying that it crashed), and then
the CD is unusable of course.

It looked like a deadlock, but I didn't watch the CPU usage to make
sure.

I didn't try other possibilities. I don't mind destroying some other CDs
for testing, if I get told what other cases to try.

This is on ubuntu 12.04, nautilus 1:3.4.2-0ubuntu4

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1067450

Title:
  burning a cd + renaming a folder at the same time causes freeze then
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1067450/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 953221] Re: UMAX Astra 1220U scanner support stopped working

2012-09-17 Thread Mathieu L BOUCHARD 
The problem that I have is not that the scanner is not detected. I might
have had that problem long ago but I didn't report it and don't remember
it. The problem I reported in the description of this bug is really that
the pixels scanned are improperly aligned (sometimes called a Shear
transformation). This is the kind of problem that happens when the
number of columns of the image is not counted correctly, such that the
driver and the device disagree on that number but are oblivious about
it. The slope of 1/3 I get means that the driver's image is missing 3
columns compared to what the scanner provides.

Yesterday, I plugged that scanner again for the first time since March
(which is why I only reply now) and then I realised that the problem
happens in 300 dpi, and something worse (lower slope) happens with 600
dpi, but 150 dpi is fine.

The shear is also accompanied by a color offset problem but I didn't
measure it and I suppose that it might be another consequence of the
same bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953221

Title:
  UMAX Astra 1220U scanner support stopped working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/953221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 953221] Re: UMAX Astra 1220U scanner support stopped working

2012-09-17 Thread Mathieu L BOUCHARD 
I tried it again with something that contained colour (yesterday's test
was nearly a black-and-white sheet) and now I see that the large
diagonal stripes also have wrong colours. The first triangle at the top
has correct colors, but as the sheared pixels wrap around, they seem to
have suffered large hue shifts, which is probably the result of making
each pixel out of two different neighbouring pixels while confusing
R,G,B channels.

I also just tried the «scanimage» command (from sane-utils) for the
first time and it has the same problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953221

Title:
  UMAX Astra 1220U scanner support stopped working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/953221/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs