[Bug 1954939] [NEW] Cannot open additional instances of the same file with the same name inside a zip archive

2021-12-15 Thread GB
Public bug reported:

This issue is very simple. A zip file can legally contain multiple
entries with the same name in the same path. If you attempt to open a
file that has the same name and path as another, you can only open one
of them, and cannot open the other.

An example zip file has been provided which contains two
`fabric.mod.json` files. If either one of them is double clicked within
file roller, it will only open one of them, and never the other.

example.zip
|
|
fabric.mod.json (2.1kb)
|
fabric.mod.json (484 bytes)

For me, the 484 byte file is always opened, even if you double click the
2.1kb file.

Ubuntu 21.10
file-roller 3.40.0-2

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Example zip file which can be used to demonstrate the 
issue"
   
https://bugs.launchpad.net/bugs/1954939/+attachment/5547843/+files/example.zip

** Summary changed:

- Cannot open additional instances of the same file with the same name inside a 
zip
+ Cannot open additional instances of the same file with the same name inside a 
zip archive

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

Title:
  Cannot open additional instances of the same file with the same name
  inside a zip archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1954939/+subscriptions


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

[Bug 1954939] Re: Cannot open additional instances of the same file with the same name inside a zip archive

2021-12-16 Thread GB
I cannot report it upstream, their signup system does not accept any of
my email addresses.

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

Title:
  Cannot open additional instances of the same file with the same name
  inside a zip archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1954939/+subscriptions


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

[Bug 1957711] [NEW] Switching users causes system crash

2022-01-12 Thread GB
Public bug reported:

Ubuntu 21.10

gdm3:
  Installed: 41~rc-0ubuntu2
  Candidate: 41~rc-0ubuntu2
  Version table:
 *** 41~rc-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages
100 /var/lib/dpkg/status

Steps to reproduce:

1. Log in as any user
2. In the top right of the screen, click the power icon (⏻)
3. Select [Power Off/Log Out]
4. Select [Switch User]
5. Select any user that is NOT the user which is still currently logged in
6. Operating system is now frozen, mouse and keyboard don't respond, and user 
is never logged in.
7. Pressing [CTRL] + [ALT] + [DEL] appears to cause the system to crash

Apport.log: https://pastebin.com/srFwgfAh

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

** Attachment added: "Crash log"
   
https://bugs.launchpad.net/bugs/1957711/+attachment/5553637/+files/gdm3.0.crash

** Package changed: apport (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Switching users causes system crash

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


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

[Bug 1085706] Re: pam_ecryptfs: seteuid error

2017-11-16 Thread GB
xscreenserver on Ubuntu 16.10 affected
nov. 16 14:10:13 clevo.gigi.edu xscreensaver[24025]: pam_ecryptfs: seteuid error

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

Title:
  pam_ecryptfs: seteuid error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ecryptfs/+bug/1085706/+subscriptions

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

[Bug 1628439] [NEW] login loop on lightdm-greeter

2016-09-28 Thread GB
Public bug reported:

After an upgrade of the system not possible anymore to login using 
lightdm-greeter.
Tried dpkg-reconfigure on all major DM package - no success
Looking for errors in PAM - no authentication errors
Looking for errors in syslog ;
org.gtk.vfs.Daemon[7528]: A connection to the bus can't be made

seems same problem that Bug #1571206 reported by dino99 on 2016-04-16
but with different symptoms.

Workaround ; put the system boot into text mode then "startx" works everytime
(and doesn't trigger gvfs error)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gvfs 1.28.2-1ubuntu1~16.04.1
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: MATE
Date: Wed Sep 28 11:28:04 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-06-01 (118 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "This file describe the upgrade of the system - before 
apply it works, after it fails"
   https://bugs.launchpad.net/bugs/1628439/+attachment/4750058/+files/fuck4

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

Title:
  login loop on lightdm-greeter

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

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


[Bug 1628439] Re: login loop on lightdm-greeter

2016-09-28 Thread GB
** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+attachment/4750062/+files/fuck6

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

Title:
  login loop on lightdm-greeter

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

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


[Bug 1628439] Re: login loop on lightdm-greeter

2016-09-28 Thread GB
** Attachment added: "auth"
   
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1628439/+attachment/4750063/+files/fuck7

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

Title:
  login loop on lightdm-greeter

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

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


[Bug 1628439] Re: login loop on lightdm-greeter

2017-03-17 Thread GB
I realized that .xinputrc was corrupted due to the fact that im-config was 
using an non official md5sum build!
For that reason, the bus couldn't sucessfully complete its initialization and 
gvfs couldn't launch itself.
With the use the official md5sum (from coreutils), the .xinputrc was corrected 
and I could launch the graphical environment automaticaly again without issue 
(sudo systemctl set-default graphical.target --force)
The gvfs error was gone away from syslog.

Guillaume

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

Title:
  login loop on lightdm-greeter

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

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


[Bug 1628439] Re: login loop on lightdm-greeter

2017-03-17 Thread GB
Not a bug. corrupted xinputrc

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

Title:
  login loop on lightdm-greeter

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

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