Bug#899039: libgit2 0.27 transition
Package: calligra Version: 1:3.1.0+dfsg-2 Severity: important Dear Maintainer, libgit2 0.27 is now available in experimental. Please make sure your package is ready for this version by the time we upload this package to unstable in one to two weeks. The severity of this report will be raised to serious once libgit2 0.27 is uploaded to unstable. Thanks Praveen
Bug#898888: libgit2 0.27 transition
Package: ktexteditor Version: 5.45.0-1 Severity: important Dear Maintainer, libgit2 0.27 is now available in experimental. Please make sure your package is ready for this version by the time we upload this package to unstable in one to two weeks. The severity of this report will be raised to serious once libgit2 0.27 is uploaded to unstable. Thanks Praveen
Bug#832649: multi-display is broken (menu and panel appears only on external display)
On 2017, ഫെബ്രുവരി 26 3:40:00 PM IST, Niels Thykier wrote: >Hi Pirate, > >Did you have a chance to test whether this bug still persists? Sorry I won't be able to confirm it as I'm traveling and also I switched to gnome. >Thanks, >~Niels -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#832649: multi-display is broken (menu and panel appears only on external display)
On 09/06/2016 12:06 PM, Maximiliano Curia wrote: > This should be handled by kscreen, so I'm reassigning the issue. I can't > reproduce the issue here (with an Intel HD Graphics 3000), I'm not sure > if this is somehow fixed in 5.7.4 or it was caused by something external > (hardware or dependency). Is the issue still reproducible using kscreen > 5.7.4? Yes, its still the same problem. Even booting without HDMI monitor gives the same result. Another user get the panel correctly. Can I remove some config files to fix this? > What shows the xrandr output before and after unplugging the hdmi cable? Before: pravi@nishumbha:~$ xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192 eDP-1 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 293mm x 165mm 1920x1080 60.00*+ 59.9340.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 HDMI-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 476mm x 267mm 1920x1080 60.00*+ 50.0059.94 1920x1080i60.0050.0059.94 1280x1024 75.0260.02 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 After: pravi@nishumbha:~$ xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1920x1080 60.00*+ 59.9340.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1360x768 59.8059.96 1152x864 60.00 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 960x600 60.00 960x540 59.99 800x600 60.0060.3256.25 840x525 60.0159.88 800x512 60.17 700x525 59.98 640x512 60.02 720x450 59.89 640x480 60.0059.94 680x384 59.8059.96 576x432 60.06 512x384 60.00 400x300 60.3256.34 320x240 60.05 HDMI-1 disconnected (normal left inverted right x axis y axis) > Searching in the upstream bugs I found this one: > https://bugs.kde.org/show_bug.cgi?id=366067 I tried removing .local/share/kscreen and restart the machine. Is there any other file I can try and remove? Now the panel has moved to laptop screen once I connect the HDMI monitor (I made Laptop screen as primary in system settings). But if I remove the HDMI cable, the panel vanishes. > That might be related, sadly, while it claims that's fixed for 5.8, it > doesn't point to the corresponding commits, so we can only wait for 5.8. Lets hope that fixes it. > Happy hacking, signature.asc Description: OpenPGP digital signature
Bug#834401: sddm cannot set per user desktop choices
On 2016, സെപ്റ്റംബർ 6 11:42:37 AM IST, Maximiliano Curia wrote: >Sorry, this is bug alright, it's annoying, but still, it's a bug, it >doesn't >merit a grave severity. > Alright. But isn't being able to choose a desktop environment a core functionality of a display manager?
Bug#834401: sddm cannot set per user desktop choices
package: sddm version: 0.13.0-1 severity: grave I have two users in my system and when using sddm, each user has to select their preferred desktop session **EVERY** single time. One user wants KDE/Plasma and another GNOME. When first users selects GNOME and logout, the second user also gets GNOME, even when they have selected KDE/Plasma as their preferred session in previous login. signature.asc Description: OpenPGP digital signature
Bug#832649: multi-display is broken (menu and panel appears only on external display)
package: systemsettings version: 4:5.7.0-1 severity: grave I have connected an HDMI monitor to my laptop and the menu and panel appears on the HDMI monitor, but when I remove the HDMI cable, the menu and panel does not appear on the laptop screen. I have to use run command and alt tab as a fallback. But I miss notifications, especially the power status and network status. kwin_x11 is the window manager. signature.asc Description: OpenPGP digital signature
Bug#813410: lock screen is not working when logged into gnome from sddm
Control: reassign -1 gnome-shell Control: reopen -1 Reassigning to gnome-shell -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#813410: lock screen is not working when logged into gnome from sddm
On Tuesday 02 February 2016 04:49 PM, Tim wrote: > > > On 02/02/16 04:15, Pirate Praveen wrote: >> package: sddm, gdm3, gnome-session >> severity: important >> >> Now it seems gnome session can lock screen only if logged in from gdm3 >> (isn't there a standard for display managers? is gnome breaking the >> standard of sddm not implementing a new standard? can't changes be >> better coordinated among DEs, can't we use freedesktop.org?). It makes >> the whole system insecure as laptops when left unattended could be >> misused by anyone without auto lock. > gnome-shell and gdm3 are quite tightly coupled, however in the case you don't > want to use gdm, you should be able to use gnome-screensaver or > xscreensaver for screen locking I used xlock as a workaround, but gnome-shell should fallback to using gnome-screensaver if gdm3 is not available. Keeping the machines (laptops) unlocked is not a good default, especially when suspended. This is basic functionality we are talking about and not some exotic nice to have feature. >> >> Same issue for switch user. > There is no standard for user switching, gdm, lightdm and probably sddm all > have their own interfaces for user switching. It would be good to have a standard and I think debian gdm maintainers are the right people to initiate - being in a position to support multiple DEs, such a standard. signature.asc Description: OpenPGP digital signature
Bug#813410: lock screen is not working when logged into gnome from sddm
[Copying -devel for wider comments] On 2016, ഫെബ്രുവരി 2 10:25:56 AM IST, Pirate Praveen wrote: > > >On 2016, ഫെബ്രുവരി 2 1:11:28 AM IST, Andreas Henriksson > wrote: >>Hello Pirate Praveen. >> >>On Mon, Feb 01, 2016 at 10:45:11PM +0530, Pirate Praveen wrote: >>> package: sddm, gdm3, gnome-session >>> severity: important >>> >>> Now it seems gnome session can lock screen only if logged in from >>gdm3 >>> (isn't there a standard for display managers? is gnome breaking the >>> standard of sddm not implementing a new standard? can't changes be >>> better coordinated among DEs, can't we use freedesktop.org?). It >>makes >>> the whole system insecure as laptops when left unattended could be >>> misused by anyone without auto lock. >>> >>> Same issue for switch user. >> >>Not sure why you think things will continue to work if you just >>replace random components of GNOME like this. You can replace >>anything you want, but if it breaks you get to keep all the pieces. >>The lock screen (et.al.) not working if you use another DM is >>a well known issue. I'm not sure if particular component >>can be "blamed" for this, since gnome-shell and gdm interaction >>isn't something all other DMs are in any way required to >>implement. Did SDDM claim it was a drop-in replacement for GDM? >>If so, please file a bug against SDDM. > >All right. Let every project stay isolated and not care about >interoperability. > >A display manager has always been about managing multiple DEs. I believe being able to lock screen is a basic feature of any DE. If gnome-shell does not work with other DEs, and if neither gnome-shell and DM developers don't care about interoperability, should we not add conflicts with all DMs except for gdm for gnome-shell? >>Regards, >>Andreas Henriksson -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#813410: lock screen is not working when logged into gnome from sddm
On 2016, ഫെബ്രുവരി 2 1:11:28 AM IST, Andreas Henriksson wrote: >Hello Pirate Praveen. > >On Mon, Feb 01, 2016 at 10:45:11PM +0530, Pirate Praveen wrote: >> package: sddm, gdm3, gnome-session >> severity: important >> >> Now it seems gnome session can lock screen only if logged in from >gdm3 >> (isn't there a standard for display managers? is gnome breaking the >> standard of sddm not implementing a new standard? can't changes be >> better coordinated among DEs, can't we use freedesktop.org?). It >makes >> the whole system insecure as laptops when left unattended could be >> misused by anyone without auto lock. >> >> Same issue for switch user. > >Not sure why you think things will continue to work if you just >replace random components of GNOME like this. You can replace >anything you want, but if it breaks you get to keep all the pieces. >The lock screen (et.al.) not working if you use another DM is >a well known issue. I'm not sure if particular component >can be "blamed" for this, since gnome-shell and gdm interaction >isn't something all other DMs are in any way required to >implement. Did SDDM claim it was a drop-in replacement for GDM? >If so, please file a bug against SDDM. All right. Let every project stay isolated and not care about interoperability. A display manager has always been about managing multiple DEs. >Regards, >Andreas Henriksson -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Bug#813410: lock screen is not working when logged into gnome from sddm
package: sddm, gdm3, gnome-session severity: important Now it seems gnome session can lock screen only if logged in from gdm3 (isn't there a standard for display managers? is gnome breaking the standard of sddm not implementing a new standard? can't changes be better coordinated among DEs, can't we use freedesktop.org?). It makes the whole system insecure as laptops when left unattended could be misused by anyone without auto lock. Same issue for switch user. signature.asc Description: OpenPGP digital signature
Bug#813409: sddm does not allow entering username manually
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 package: sddm version: 0.13.0-1 severity: important It is regression from kdm. I have a user with uid less than 1000 and it is not listed in sddm. kdm was perfect, gdm3 had an option to enter, but sddm is unusable for me. Same would be for root login. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWr5FzAAoJEM4fnGdFEsIqi0kP/26zLj3Gp3cwifUxasFsaPq0 bsRGvrCdFx/3WBjMz0Vh4MbrdilGlLsSZChd34FhUa4WBoGVeWlPHpfi2UX81DTS R4UaUdOEYbRJ8RCTrKWfoUTZtjzsvt5leh5sI8Gms1AgYDa9rBg8sn0Epzb2faSD 7FeXe+McALNVLeA6f257SLkhahcqfj4lAJl0lcdxbSC+XXzS4W1mMqCkRMVJZiJZ +PmVmCCNXQSwJx/+JPyRn5DXDMdeVfBYtfu8B7U8IpRahAcrNGvZhtjR8QbAP0ce KgUZaePzdN+zsLCrojio1YDN15ntfFI5kbMxRl641QiZZDyOLtGaKUQFydpZbPg4 x14bCef7IFkWqquaSNIERVl/olmmh66L/FnoNdng3idDsPwgXym8wzDEx2fKVDJL U6YKcYlDl6+eaz5P49xGZt51Cn9EK21jWv1BLXew3ZslV+bugnXUEEJJ/xjcK4Um K+IVEwJSw4BYp11eNIGHwlOnSK6peG+CISzG/NOIdZcimhpeTAAi/riyLi6YKUxP 6NRfA3IVplG8wygISPvIY8g8QdrJjPN5ELgtzWMFPCEf7BZ8PuImL+Lhdl/FXOUL hWQOgiUjbcO8vnq78PCdzAGEpbnOLu3QMMF8i7QQKz9KMJgfhZDdzA57pN5NbRFH PcANabZvehChTWfByRBO =lW5J -END PGP SIGNATURE-